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

CVE-2026-14645

MEDIUM · 5.1 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 →
57/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 does not validate the destination of the "Webhook: Global" capability's configured URL before making an outbound HTTP request, allowing a user holding the Capability Administration permission to cause the server to send requests to internal network locations (Server-Side Request Forgery). This permission is granted by role assignment, independent of authentication status, so an unauthenticated user could also trigger this behavior if the anonymous role has been granted the permission.

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's 'Webhook: Global' capability lacks URL destination validation before making outbound HTTP requests, enabling Server-Side Request Forgery (SSRF). Any user with Capability Administration permission—including unauthenticated users if the anonymous role holds this permission—can cause the server to make requests to internal network locations.

MitigationImplement strict URL validation to restrict webhook destinations to approved external domains/addresses, and review and restrict the Capability Administration permission especially from the anonymous role.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/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 version
    Log into the Nexus web UI as an administrator and navigate to 'Administration' > 'System' > 'Information', or query the API at /service/rest/v1/system/api to retrieve the installed version number
    Affected if The installed version falls within the affected version range for CVE-2026-14645 (check against official Nexus release notes for this vulnerability)
  2. Verify Webhook: Global capability is enabled
    In the Nexus web UI, go to 'Administration' > 'Capabilities' and locate any capability with the type 'Webhook: Global' in the list. Confirm its status is 'Enabled'
    Affected if The Webhook: Global capability exists and is in 'Enabled' status, making the SSRF vulnerability accessible
  3. Check Capability Administration permission assignment
    Navigate to 'Administration' > 'Security' > 'Roles' and review which roles are assigned the 'Capability Administration' privilege. Also check 'Administration' > 'Security' > 'Users' to see direct role assignments
    Affected if Any user role (other than the default admin) is granted the Capability Administration permission, or the anonymous role specifically holds this permission
  4. Verify anonymous access configuration
    Go to 'Administration' > 'Security' > 'Anonymous Access' and confirm whether anonymous access is enabled. If enabled, cross-reference which roles the anonymous user inherits
    Affected if Anonymous access is enabled and the anonymous user inherits a role with Capability Administration permission, allowing unauthenticated exploitation

You are affected if your Nexus Repository 3 version is vulnerable AND the Webhook: Global capability is enabled AND either a non-admin user or the anonymous user has Capability Administration permission.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation to restrict webhook destinations to approved external domains/addresses, and review and restrict the Capability Administration permission especially from the anonymous role.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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