Skip to main content
VulnerabilityPublished

CVE-2026-92215: a2ui-project a2ui · Server-Side Request Forgery

Affects a2uiSource GCVE Database

0
Compare
Authoritative record:CVE-2026-92215· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHuba2ui-project/a2uipkg:github/a2ui-project/a2uiOther threatsAffected
  • <=0.10.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch has been identified for this vulnerability (commit 2bb8423060308bbdea8ba468dabed4fc256d18ea). It is recommended to deploy this patch to remediate the issue. No vendor advisory content was provided to indicate alternative mitigations or if the patch is already integrated in newer versions.

Description

A server-side request forgery (SSRF) vulnerability exists in a2ui-project a2ui up to version 0.10.7. The flaw is in the httpx.get function within the FileResolver component, allowing remote attackers to initiate SSRF attacks. A patch has been identified to fix this issue.

References

Community reviews

Loading reviews…