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

CVE-2026-7494

MEDIUM · 5.3 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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
Nexus Repository 3 is vulnerable to Server-Side Request Forgery (SSRF) via the SSL Certificate Retrieval endpoint. A user holding the nexus:ssl-truststore:read permission could cause the server to initiate outbound connections to internal or otherwise restricted network hosts. This issue affects Nexus Repository 3.0.0 through versions prior to 3.94.0.

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

Nexus Repository 3 contains an SSRF vulnerability in its SSL Certificate Retrieval endpoint. Users possessing the nexus:ssl-truststore:read permission can manipulate the server into making outbound connections to internal or otherwise restricted network hosts, potentially exposing internal services and infrastructure.

MitigationUpgrade Nexus Repository 3 to version 3.94.0 or later. Additionally, review and restrict the nexus:ssl-truststore:read permission to only essential personnel and implement network segmentation to limit potential internal reconnaissance.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify Nexus Repository 3 installation and version
    Locate the Nexus installation directory and check the version. The version is typically found in 'nexus/WEB-INF/lib/nexus-common-X.XX.X.jar' or in the 'nexus-system' properties file. Alternatively, access the Nexus UI and check the 'System' > 'Information' page.
    Affected if The installed version is any version prior to 3.94.0.
  2. Confirm SSL Certificate Retrieval endpoint exists
    Verify that the SSL Certificate Retrieval endpoint is present in the Nexus 3 installation. This endpoint is typically accessible at '/service/rest/v1/ssl/truststore' via the REST API.
    Affected if The endpoint responds to requests, indicating the vulnerable component is present.
  3. Check for nexus:ssl-truststore:read permission assignments
    Navigate to Administration > Security > Roles in the Nexus UI and review all defined roles. Additionally, check Administration > Security > Users to see which users have direct permission assignments. Identify any roles or users granted the 'nexus:ssl-truststore:read' permission.
    Affected if Any user or role possesses the nexus:ssl-truststore:read permission.
  4. Verify ability to trigger outbound connections
    Using an account with the nexus:ssl-truststore:read permission, attempt to access the SSL Certificate Retrieval endpoint with a target URL pointing to an internal host (for example, http://internal-network-host or an IP behind a firewall). Observe if the server attempts to connect to the specified internal host.
    Affected if The server successfully makes an outbound connection to an internal or restricted host through this endpoint.

Your environment is affected if Nexus Repository 3 version is before 3.94.0 AND the nexus:ssl-truststore:read permission is assigned to at least one user or role.

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 Nexus Repository 3 to version 3.94.0 or later. Additionally, review and restrict the nexus:ssl-truststore:read permission to only essential personnel and implement network segmentation to limit potential internal reconnaissance.

Recommended fix High confidence

3.94.0 or later

  1. Upgrade Nexus Repository 3 to version 3.94.0 or later to remediate the SSRF vulnerability in the SSL Certificate Retrieval endpoint

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7494 — 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-2026-7494 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