CVE-2025-25235VulnerabilityPublished 11 Aug 2025

CVE-2025-25235: Omnissa Secure Email Gateway · Server-Side Request Forgery (SSRF)

Affects Omnissa Secure Email GatewaySource CVE Database V5

Not known to be exploited · CVSS 8.6 High : upgrade to 2503 or 2.32 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.6High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2503, 2.32

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

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

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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Aug 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-26.

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

Upgrade Omnissa Secure Email Gateway to 2503 or 2.32.

Affected software

Product	Affected	Fixed in
Omnissa Secure Email Gateway	Affected <2.32 <2503	Fixed in 2.32 2503

AI-suggested

European organizations should immediately assess their deployment of Omnissa Secure Email Gateway products and identify versions prior to 2.32 on Windows and prior to 2503 on UAG. Although no official patches are currently listed, organizations should monitor Omnissa's advisories closely for forthcoming security updates and apply them promptly once available. In the interim, network-level mitigations can reduce risk: restrict outbound HTTP/HTTPS traffic from the SEG server to only necessary external endpoints using firewall rules; implement strict egress filtering to prevent unauthorized internal network access; and employ network segmentation to isolate the SEG from sensitive internal systems. Additionally, review and harden SEG configuration settings to disable any unnecessary URL fetching or proxying features that could be abused. Deploying Web Application Firewalls (WAFs) or Intrusion Detection/Prevention Systems (IDS/IPS) with SSRF detection capabilities can help identify and block suspicious requests. Conduct thorough logging and monitoring of SEG network activity to detect anomalous outbound requests indicative of SSRF exploitation attempts. Finally, educate security teams about SSRF risks and prepare incident response plans to quickly contain and remediate potential exploitation.

Description

Server-Side Request Forgery (SSRF) in Omnissa Secure Email Gateway (SEG) in SEG prior to 2.32 running on Windows and SEG prior to 2503 running on UAG allows routing of network traffic such as HTTP requests to internal networks.

Impact

For European organizations, the impact of CVE-2025-25235 is significant due to the widespread use of secure email gateways as a frontline defense against email-borne threats. Successful exploitation could allow attackers to bypass network segmentation and access internal resources, potentially exposing sensitive personal data protected under GDPR and other privacy regulations. Confidentiality breaches could lead to regulatory penalties, reputational damage, and loss of customer trust. Additionally, internal services accessed via SSRF could include databases, internal APIs, or management consoles, increasing the risk of further compromise. The lack of required authentication and user interaction means attackers can exploit this vulnerability remotely and autonomously, increasing the threat level. European organizations in sectors such as finance, healthcare, government, and critical infrastructure are particularly at risk given their reliance on secure email gateways and the sensitivity of their data. The SSRF could also be leveraged as a stepping stone for advanced persistent threats (APTs) targeting European entities, especially in the context of geopolitical tensions. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the high CVSS score and scope change indicate that the vulnerability could be weaponized effectively once exploit code becomes available.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

omnissa.com/omsa-2025-0003/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Aug 2025, 01:43 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats