Answer in brief
CVE-2025-52556 records a Critical severity (CVSS 0.0) vulnerability in rfc3161-client has insufficient verification for timestamp response signatures. The current sources do not mark it as known exploited. The current feed maps rfc3161-client (pip). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rfc3161-client (pip). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rfc3161-clientpip | <=1.0.2 | 1.0.3 |
Published upstream
Jun 20, 2025
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
### Impact `rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA. ### Patches Users should immediately upgrade to `rfc3161-client` 1.0.3 or later. ### Workarounds There is no workaround possible. Users should immediately upgrade to a fixed version.
Quoted source text, attributed separately from HOL analysis.