CVE-2026-33753
- Source
- https://cve.org/CVERecord?id=CVE-2026-33753
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-33753.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-33753
- Aliases
- Downstream
- Related
- Published
- 2026-04-08T14:54:59.704Z
- Modified
- 2026-07-13T16:43:08.687187641Z
- Severity
-
- 6.2 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
- Summary
- Improper Certificate Validation in rfc3161-client
- Details
-
rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to 1.0.6, an Authorization Bypass vulnerability in rfc3161-client's signature verification allows any attacker to impersonate a trusted TimeStamping Authority (TSA). By exploiting a logic flaw in how the library extracts the leaf certificate from an unordered PKCS#7 bag of certificates, an attacker can append a spoofed certificate matching the target common_name and Extended Key Usage (EKU) requirements. This tricks the library into verifying these authorization rules against the forged certificate while validating the cryptographic signature against an actual trusted TSA (such as FreeTSA), thereby bypassing the intended TSA authorization pinning entirely. This vulnerability is fixed in 1.0.6.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-295" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33753.json" }- References
Affected packages
Git / github.com/trailofbits/rfc3161-client
Affected ranges
- Type
- GIT
- Repo
- https://github.com/trailofbits/rfc3161-client
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "extracted_events": [ { "introduced": "0" }, { "fixed": "1.0.6" } ], "cpe": "cpe:2.3:a:trailofbits:rfc3161-client:*:*:*:*:*:*:*:*", "source": [ "AFFECTED_FIELD", "CPE_RANGE" ] }