Skip to main content
VulnerabilityPublished

CVE-2026-73297: microsoft UFO · Server-Side Request Forgery (SSRF)

Affects microsoft UFOSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.0.8 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 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 9 Nov 2026.

What to do

Upgrade UFO and microsoft/UFO to 3.0.8.

Affected software

ProductAffectedFixed in
microsoftUFOAffected
  • <3.0.8
Fixed in
  • 3.0.8
GitHubmicrosoft/UFOpkg:github/microsoft/UFOOther threatsAffected
  • <3.0.8
Fixed in
  • 3.0.8

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

AI-suggested

Upgrade to Microsoft UFO version 3.0.8 or later, where the SSRF protection correctly blocks the specified IPv6 prefixes and re-checks embedded IPv4 addresses. No other mitigation guidance is provided. Patch status is confirmed fixed in version 3.0.8.

Description

Microsoft UFO open-source framework for intelligent automation across devices and platforms. Prior to 3.0.8, _is_blocked_ip in ufo/utils/url_security.py did not block NAT64 prefixes 64:ff9b::/96 and 64:ff9b:1::/48, the 6to4 prefix 2002::/16, or the Teredo prefix 2001::/32 and did not re-check embedded IPv4 destinations, allowing an unauthenticated remote attacker who can influence URLs processed by validate_url to bypass the SSRF guard and reach cloud metadata, internal services, or localhost. This issue is fixed in version 3.0.8.

References

Community reviews

Loading reviews…