How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability low.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Attack vector: Local — a local account, shell or session on the host is needed.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
- Integrity impact: Low — limited, and the attacker does not choose what is affected.
- Availability impact: Low — limited, and the attacker does not choose what is affected.
Weakness class
CVE-2026-16129 is classified as CWE-183: Permissive List of Allowed Inputs. The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input…
Affected software
CVE-2026-16129 is recorded against 1 package.
Timeline and source
Published on 18 July 2026 and last revised on 22 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com
github.com
vuldb.com
vuldb.com
vuldb.com
vuldb.com
vuldb.com
Other advisories for this package
unknown 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-183: Permissive List of Allowed Inputs) in other software:
