Quick answers
- Is CVE-2026-92215 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92215 being exploited in the wild.
- How severe is CVE-2026-92215?
- High severity, with a CVSS score of 7.3, published 16 September 2026.
- Which products and versions are affected?
- a2ui-project a2ui up to 0.10.7.
- Is there a fix for CVE-2026-92215?
- A patch was published on 2026-08-26: Patch commit 2bb8423060308bbdea8ba468dabed4fc256d18ea Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92215 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92215?
- 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
A server-side request forgery (SSRF) vulnerability exists in the FileResolver component (file_resolve/file_resolver.py) due to improper validation of URLs passed to httpx.get. The vulnerable code does not adequately restrict which hosts can be accessed via HTTP requests, allowing attackers to craft malicious URLs that redirect to internal or restricted network resources. The fix involves defaulting allowed_hosts to an empty list, validating IP addresses on redirects, and mitigating DNS rebinding attacks by including proper validation of hostnames and schemes. No authentication is required to exploit this vulnerability, making it remotely accessible. The patch is available in commit 2bb8423060308bbdea8ba468dabed4fc256d18ea.
Affected products
- a2ui-project a2ui up to 0.10.7
Timeline
- 2026-09-16: disclosed
- 2026-08-26: patched: Patch commit 2bb8423060308bbdea8ba468dabed4fc256d18ea