Skip to main content
VulnerabilityPublished Updated

CVE-2025-52556: rfc3161-client has insufficient verification for timestamp response signatures

Affects rfc3161-clientSource GCVE Database

0
Compare
Authoritative record:CVE-2025-52556· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.0.3 as a priority.

Data as of 16 Nov 2026, 17:50 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 15 Nov 2026.

What to do

Upgrade rfc3161-client to 1.0.3.

Affected software

ProductAffectedFixed in
PyPIrfc3161-clientAffected
  • <1.0.3
Fixed in
  • 1.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should immediately upgrade to rfc3161-client version 1.0.3 or later, where the signature verification logic has been corrected. There are no workarounds available for this vulnerability, so upgrading is the only effective mitigation.

Description

rfc3161-client versions 1.0.2 and earlier have a vulnerability in their timestamp response signature verification. The flaw allows attackers to bypass proper signature validation by introducing any timestamp response signature that chains up to a trusted root certificate, without verifying the signature against the leaf certificate. This can lead to acceptance of forged timestamp responses. The issue is fixed in version 1.0.3, and no workaround exists other than upgrading.

References

Community reviews

Loading reviews…