CVE-2025-55322VulnerabilityPublished 24 Sep 2025Updated 20 Feb 2026

CVE-2025-55322: Microsoft OmniParser · Binding to an Unrestricted IP Address

Affects Microsoft OmniParserSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Microsoft OmniParser	Affected =1.0.0	Fixed in–

AI-suggested

To mitigate CVE-2025-55322, organizations should immediately restrict network exposure of OmniParser services by configuring firewalls and network access controls to limit inbound connections only to trusted IP addresses and internal networks. Disable or block OmniParser instances from binding to all interfaces; if possible, configure the software to bind only to specific, trusted IP addresses or localhost. Employ network segmentation to isolate vulnerable systems from critical infrastructure and sensitive data stores. Monitor network traffic for unusual connections to OmniParser ports and implement intrusion detection/prevention systems with signatures targeting anomalous OmniParser activity. Maintain strict patch management and subscribe to Microsoft security advisories to apply updates promptly once patches are released. Consider deploying application-layer gateways or reverse proxies that enforce authentication and access control in front of OmniParser services. Conduct regular vulnerability scans and penetration tests to identify exposure. Finally, develop incident response plans specific to OmniParser compromise scenarios to reduce response time in case of exploitation.

Description

Binding to an unrestricted ip address in GitHub allows an unauthorized attacker to execute code over a network.

Impact

The impact of CVE-2025-55322 is significant for organizations deploying Microsoft OmniParser 1.0.0, especially those exposing the service to untrusted networks such as the internet or large internal networks without segmentation. Successful exploitation can lead to unauthorized remote code execution, allowing attackers to compromise system confidentiality by accessing sensitive data, integrity by modifying or injecting malicious code, and availability by disrupting or crashing the service. This can result in data breaches, lateral movement within networks, and potential full system compromise. Enterprises relying on OmniParser for critical data parsing or processing tasks may face operational disruptions and reputational damage. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the risk of automated attacks or wormable scenarios if combined with other vulnerabilities. While no known exploits exist yet, the vulnerability's characteristics make it a prime target for attackers once exploit code becomes available.

CWE-1327Binding to an Unrestricted IP Address (opens in a new tab)
Base weakness
The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.
System Configuration
Assign IP addresses that are not 0.0.0.0.
System Configuration · Firewall
Unwanted connections to the configured server may be denied through a firewall or other packet filtering measures.
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55322 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Feb 2026, 21:36 UTC

WeaknessesCWE-1327

Technical details

References

Community reviews

Related threats