CVE-2026-17593 in Nexus Repositoryinformation

Résumé

par MITRE • 07/08/2026

An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against the set of registered realms. Because unrecognized entries were persisted and re-evaluated on every realm load via a legacy code path, this could result in unintended code executing inside the Nexus Repository process, and in some cases a persistent authentication lockout that was not visible through the administrative UI.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Responsable

Sonatype

Réserver

27/07/2026

Divulgation

07/08/2026

Modérer

accepté

Entrée

VDB-387032

CPE

prêt

EPSS

0.00000

KEV

non

Activités

très faible

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!