Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
rfc3161-client versions before 1.0.3 do not fully verify timestamp response (TSR) signatures. The library checks the embedded certificate chain up to a trusted root but does not check the TSR's own signature against the leaf certificate, so an attacker can supply an arbitrary signature alongside a valid chain and have the response accepted. Upgrade to rfc3161-client 1.0.3 or later; the source lists no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.3 | Critical | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0017, the 6th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6qhv-4h7r-2g9m
- OSV: GHSA-6qhv-4h7r-2g9m
- github.com/trailofbits/rfc3161-client/security/advisories/GHSA-6qhv-4h7r-2g9m
- nvd.nist.gov/vuln/detail/CVE-2025-52556
- github.com/trailofbits/rfc3161-client/commit/724a184f953e3f171f85cb223871172b41b0d0dc
- github.com/trailofbits/rfc3161-client
- pypi.org/project/rfc3161-client
- github.com/advisories/GHSA-6qhv-4h7r-2g9m