Skip to main content
CVE-2026-69192VulnerabilityPublished

Microsoft · ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-69192· High 7.7

Not known to be exploited · CVSS 7.7 High : upgrade to 10.3.1 soon.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 10.3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 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 16 Nov 2026.

What to do

Upgrade ip-address to 10.3.1.

Affected software

ProductAffectedFixed in
beaugundersonip-addressAffected
  • <10.3.1
Fixed in
  • 10.3.1
npmip-addresspkg:npm/ip-addressOther threatsAffected
  • <10.3.1
Fixed in
  • 10.3.1

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

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…