How severe is CVE-2025-48995?

CVE-2025-48995 has a CVSS 4.0 base score of 6.9, rated medium severity.

Is CVE-2025-48995 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-48995?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-48995 have an EU (EUVD) identifier?

Yes. CVE-2025-48995 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16676.

When was CVE-2025-48995 published?

CVE-2025-48995 was published on 2025-06-02 and last updated on 2026-06-17.

CVE-2025-48995

CVE-2025-48995 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: Medium (CVSS 4.0 base score 6.9)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-16676
Weakness: CWE-208
Published: 2025-06-02
Last modified: 2026-06-17

Description

SignXML is an implementation of the W3C XML Signature standard in Python. When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (`signxml.XMLVerifier.verify(require_x509=False, hmac_key=...`), versions of SignXML prior to 4.0.4 are vulnerable to a potential timing attack. The verifier may leak information about the correct HMAC when comparing it with the user supplied hash, allowing users to reconstruct the correct HMAC for any data.

Frequently asked questions

What is CVE-2025-48995?: SignXML is an implementation of the W3C XML Signature standard in Python. When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (`signxml.XMLVerifier.verify(require_x509=False, hmac_key=...`), versions of SignXML prior to 4.0.4 are vulnerable to a potential timing attack. The verifier may leak information about the correct HMAC when comparing it with the user supplied hash, allowing users to reconstruct the correct HMAC for any data.
How severe is CVE-2025-48995?: CVE-2025-48995 has a CVSS 4.0 base score of 6.9, rated medium severity.
Is CVE-2025-48995 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-48995?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-48995 have an EU (EUVD) identifier?: Yes. CVE-2025-48995 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16676.
When was CVE-2025-48995 published?: CVE-2025-48995 was published on 2025-06-02 and last updated on 2026-06-17.

References

Other CWE-208 vulnerabilities

CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2025-53940 — High (CVSS 8.5): Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central…
CVE-2026-47784 — High (CVSS 8.1): In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because…
CVE-2026-47783 — High (CVSS 8.1): In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a…
CVE-2026-42602 — High (CVSS 8.1): azureauthextension is the Azure Authenticator Extension. From 0.124.0 to 0.150.0, a server-side authentication bypass…

Browse all CWE-208 vulnerabilities →