CVE-2025-59432VulnerabilityPublished 12 May 2026Updated 10 Nov 2026

SUSE · Security update for ongres-scram, ongres-stringprep, plexus-testing, maven, maven-doxia, mojo-parent, sisu

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2025-59432· Medium 6.6

Not known to be exploited · CVSS 6.6 Medium.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 4.0 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

Description

This update for ongres-scram, ongres-stringprep, plexus-testing, maven, maven-doxia, mojo-parent, sisu fixes the following issues: Changes in ongres-scram: - Version 3.2 * Fix Timing Attack Vulnerability in SCRAM Authentication (bsc#1250399, CVE-2025-59432) * Updated dependencies and maven plugins * Use central-publishing-maven-plugin to deploy to Maven Central. - Do not create multirelease jar if the only Java 9+ class file is module-info.class Changes in ongres-stringprep: - Do not create multirelease jar if the only Java 9+ class file is module-info.class Changes in plexus-testing: - The build without tests does not need the full junit5; the junit5-minimal (built with ant) is enough Changes in maven: - Upgrade to upstream version 3.9.14 * Bug Fixes + plexus-testing dependencies should be used in test scope - Upgrade to upstream version 3.9.13 * Bug Fixes + Bug: SecDispatcher is managed by legacy Plexus DI + [3.9.x] MavenPluginJavaPrerequisiteChecker: Handle 8/1.8 Java version in ranges as well * Maintenance + Update Maven plugin versions in default-bindings.xml + Migrate to JUnit 5 - avoid using TestCase Changes in maven-doxia: Upgrade to upstream version 2.1.0: * New features and improvements + Distinguish between linebreaks for formatting markup and linebreaks in output + Return SinkEventAttributes instead of super class MutableAttributeSet for filterAttributes + Optionally leave fragments of internal links untouched Support strikethrough for Markdown sink + DOXIA-770: Only escape when necessary + DOXIA-760: Clarify table justification semantics and introduce new "JUSTIFY_DEFAULT" alignment + DOXIA-756: Allow to customize macro execution + DOXIA-759: Support anchors in MarkdownSink * Bug Fixes + MarkdownSink: Fix verbatim inside table cell + Make sure to emit metadata prior everything else + Convert all globally available attributes to HTML5 compliant ones + Html5BaseSink: Convert non-compliant HTML5 attributes to compliant ones + Support "name" attribute in "a" element still in XHTML5 + Never emit Markdown inside HTML context + Use JSoup to convert HTML to XHTML after parsing with Flexmark + DOXIA-764: Strip leading newline after + DOXIA-763: Distinguish between verbatim source and non-source in MarkdownSink + DOXIA-758: Consider emitComments flag in MarkdownSink + DOXIA-757: Don't strip leading "#" from link names + DOXIA-753: Do not end lists with a blank line + DOXIA-751: Linked inline code must be emitted in right order + DOXIA-749: Correctly indent and separate blocks inside list items + DOXIA-750: Properly apply inlines inside HTML blocks + DOXIA-747: Emit headings at beginning of line for Markdown * Documentation updates + Site: Convert APT to Markdown + Improve documentation of supported extensions + (doc) Fix missing references in JavaDocs * Maintenance + Cleanup tests + JUnit Jupiter best practices + Remove commons-lang3 and commons-text dependencies + feat: enable prevent branch protection rules + Cleanup pom, remove redundant dependencies + Drop almost all usages of plexus-utils + Remove not used and outdated clirr-maven-plugin + Enable Github Issues + DOXIA-772: Deprecate Sink.sectionTitle() and sectionTitle_() + DOXIA-754: Clarify method order for nested lists Changes in mojo-parent: - Do not import junit-bom in the parent. This creates unnecessary build cycles with junit5.

References

Community reviews

Loading reviews…

Exploitation evidence

Description

Technical details

References

Community reviews

Related threats