dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-25235

HIGH · 8.6 CVSS v3.1 Published 2025-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-Side Request Forgery (SSRF) in Omnissa Secure Email Gateway allows unauthenticated attackers to route HTTP requests through the SEG server to internal networks, potentially accessing internal services and bypassing network segmentation controls.

MitigationUpgrade Omnissa SEG to version 2.32 or later (Windows) or version 2503 or later (UAG). Additionally, apply network segmentation and restrict outbound connectivity from the SEG server to only necessary destinations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Omnissa SEG installation
    Locate the Omnissa Secure Email Gateway installation on the system. Common installation directories include C:\Program Files\VMware\SEG on Windows or check /opt/omnissa/seg on Linux-based appliances. Verify the product binary or service exists.
    Affected if Omnissa SEG is not installed on the system.
  2. Determine installed version
    Run the version check command for your SEG installation. On Windows, this is typically done via the SEG management interface or by checking the installed programs list. On UAG appliances, access the admin console or run the version command via SSH. Record the exact version number.
    Affected if The installed version is lower than 2.32 (Windows) or lower than 2503 (UAG).
  3. Verify network exposure
    Check the SEG network configuration to determine if the web interface or email processing services are exposed to untrusted networks. Review firewall rules, NAT configurations, and access control lists applied to the SEG server.
    Affected if The SEG management interface or processing ports are accessible from untrusted/external networks without proper filtering.
  4. Inspect for suspicious internal connections
    Review SEG logs, proxy logs, and network traffic logs for outbound connections to internal IP addresses (RFC 1918 private ranges such as 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) that were not initiated by legitimate email processing workflows. Focus on HTTP/HTTPS requests to internal systems.
    Affected if Logs show unexpected outbound HTTP requests from the SEG server to internal network resources that were not part of normal email gateway operations.

A system is affected if Omnissa SEG is installed with a version lower than 2.32 (Windows) or lower than 2503 (UAG) and the interface is exposed to untrusted networks, or if exploitation signs are present in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Omnissa SEG to version 2.32 or later (Windows) or version 2503 or later (UAG). Additionally, apply network segmentation and restrict outbound connectivity from the SEG server to only necessary destinations.

Recommended fix High confidence

SEG 2.32 for Windows or SEG 2503 for UAG

  1. Identify the current version of Omnissa Secure Email Gateway (SEG) running on your system
  2. If running on Windows: upgrade to version 2.32 or later
  3. If running on UAG (Unified Access Gateway): upgrade to version 2503 or later
  4. After upgrade, verify the new version is running and the SSRF vulnerability is remediated
  5. Review SEG configuration to ensure no unintended network routing is enabled

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data