Quick answers
- Is CVE-2026-77121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77121 being exploited in the wild.
- How severe is CVE-2026-77121?
- Informational severity, published 2 September 2026.
- Which products and versions are affected?
- Sonatype Nexus Repository 3.95.0 through 3.95.4.
- Is there a fix for CVE-2026-77121?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-77121 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-77121?
- Check whether you run Sonatype Nexus Repository at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability involves a denial-of-service condition in Sonatype Nexus Repository's Maven metadata handling. An authenticated user with deployment permissions to a hosted Maven repository can upload a POM file containing a malformed or oversized metadata field. The repository's index or metadata parser does not properly validate or limit the size of these fields, causing subsequent attempts to list or browse that specific repository's components to fail. The failure is persistent until manual administrative intervention repairs the corrupted metadata. The attack requires valid deployment credentials and targets only the specific repository receiving the malicious artifact; other repositories are unaffected.
Affected products
- Sonatype Nexus Repository 3.95.0 through 3.95.4
Timeline
- 2026-09-02: disclosed