https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 06:15:10 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-349539 EUVD-2026-349539 https://cve.radiocsirt.org/vuln/euvd-2026-349539 https://cve.radiocsirt.org/vuln/fkie_cve-2026-17593 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-17593 https://cve.radiocsirt.org/vuln/ghsa-rw8g-2688-625j <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-rw8g-2688-625j https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2713 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Sonatype Nexus Repository Manager ausnutzen, um Daten offenzulegen oder zu Manipulieren, Code auszuführen oder Rechte zu erweitern.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Sonatype Nexus Repository Manager ausnutzen, um Daten offenzulegen oder zu Manipulieren, Code auszuführen oder Rechte zu erweitern.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2713