How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs administrative privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
- Privileges required: High — administrative rights are needed first.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: High — total loss, or loss the attacker controls.
- Integrity impact: High — total loss, or loss the attacker controls.
- Availability impact: High — total loss, or loss the attacker controls.
Weakness class
CVE-2026-47619 is classified as CWE-1357: Reliance on Insufficiently Trustworthy Component. The product is built from multiple separate components, but it uses a component that is not sufficiently trusted to meet expectations for security, reliability, updateability, and maintainability.
Affected software
CVE-2026-47619 is recorded against 1 package.
Timeline and source
Published on 4 August 2026 and last revised on 7 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com
nvd.nist.gov
www.cve.org
Other advisories for this package
dynamo has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-1357: Reliance on Insufficiently Trustworthy Component) in other software:
