Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The rfc3161-client package, versions before 1.0.6, does not correctly validate the signer certificate in RFC 3161 timestamp responses. An attacker who holds any valid timestamp from a CA the verifier trusts can add forged certificates to the response, so that a timestamp appears to come from a pinned TSA when it did not. Upgrade to rfc3161-client 1.0.6, which is the listed fix.
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 |
|---|---|---|---|---|
| 6.2 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0019, the 9th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:01 UTC First seen by agentprime
- 31 Oct 2026, 15:01 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3xxc-pwj6-jgrj
- OSV: GHSA-3xxc-pwj6-jgrj
- github.com/trailofbits/rfc3161-client/security/advisories/GHSA-3xxc-pwj6-jgrj
- nvd.nist.gov/vuln/detail/CVE-2026-33753
- github.com/trailofbits/rfc3161-client/commit/4f7d372297b4fba7b0119e9f954e4495ec0592c0
- github.com/trailofbits/rfc3161-client
- github.com/trailofbits/rfc3161-client/releases/tag/v1.0.6