Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7308

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-11

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

55/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

An authenticated user with upload permission to a hosted repository can store content that causes arbitrary JavaScript to execute in the browser of any user who browses that repository directory via the HTML index page in Sonatype Nexus Repository versions 3.6.0 through versions before 3.92.0. This could allow the attacker to perform actions in the context of the victim's session.

Technical summary

dbcve analysis · high confidence

A stored XSS vulnerability in Sonatype Nexus Repository 3.x (versions 3.6.0 through before 3.92.0) allows authenticated users with upload permissions to inject malicious JavaScript into repository content. This JavaScript executes in the browsers of users who browse the affected repository directory via the HTML index page, potentially allowing session hijacking.

MitigationUpgrade Nexus Repository to version 3.92.0 or later to remediate this stored XSS vulnerability.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
Authentication: X
User interaction: P
Scope: X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/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?

dbcve checks

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

Identify installed Nexus Repository version

Access the Nexus administration interface and navigate to the System > Summary or Administration > System menu to view the running version. Alternatively, check the version file in the Nexus installation directory or query the Nexus API endpoint /service/rest/v1/status if accessible.

Affected if The installed version is 3.6.0 through 3.91.x (any version before 3.92.0)
Verify HTML repository browsing is enabled

Check the repository configuration settings in Nexus under Administration > Repositories. Look for settings related to 'HTTP' or 'browse' or 'index' that control whether repositories serve HTML directory listings.

Affected if HTML index browsing is enabled for any hosted repository that accepts uploads
Confirm user upload permissions exist

Navigate to Administration > Security > Roles and Administration > Security > Users in the Nexus UI. Review which users or roles are assigned privileges that include 'nx-repository-upload-*-*' or similar upload permissions.

Affected if Any authenticated users have upload permissions to hosted repositories

Your environment is affected if Nexus Repository 3.x is running a version between 3.6.0 and 3.91.x, HTML directory browsing is enabled, and users with upload permissions exist.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Nexus Repository to version 3.92.0 or later to remediate this stored XSS vulnerability.

Recommended fix High confidence

Nexus Repository 3.92.0

Back up your Nexus Repository 3 data directory (usually <nexus-home>/sonatype-work/nexus3)
Stop the Nexus Repository service
Download Nexus Repository 3.92.0 from the official Sonatype download page (https://help.sonatype.com/en/download.html)
Extract the new version to your installation directory, replacing the previous installation
Review release notes for any required pre-upgrade or post-upgrade steps
Start the Nexus Repository service
Verify the upgrade was successful by logging into the web UI and checking the version under 'Administration' > 'System' > 'Capabilities'

Caveat Review Sonatype release notes for 3.92.0 for any breaking changes or required migration steps before upgrading

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
Testing4.0 h
Review / QA2.0 h

14.0 hours of engineering $2,480

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-7308?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.1 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 14 hrs · Moderate

Typical engagement from $2,480

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-7308 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References