Quick answers
- Is CVE-2026-92919 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92919 being exploited in the wild.
- How severe is CVE-2026-92919?
- High severity, with a CVSS score of 8.1, published 17 September 2026.
- Which products and versions are affected?
- admin3 admin3 through 3.0.0.
- Is there a fix for CVE-2026-92919?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92919 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92919?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal flaw in the upload handler where client-supplied filenames are concatenated directly into the storage key without sanitization. The StorageServiceImpl generates a 5-character random prefix followed by the unsanitized filename; when this is resolved against the storage root using LocalStorage.store(), no containment check is performed. On Windows, attackers can use multiple dot-dot (..) path segments to escape the configured storage directory and reach parent directories. The 5-character prefix fuses with the first "..", requiring N+1 ".." groups to traverse N levels above the storage root. Exploitation requires valid authentication and is limited to Windows deployments; Linux systems fail due to per-component path resolution. An authenticated attacker can overwrite files with arbitrary content accessible to the server process, including application files or configuration.
Affected products
- admin3 admin3 through 3.0.0
Timeline
- 2026-09-17: disclosed
- other: CVE-2026-92919 assigned