Advisory record · GHSA-3xxc-pwj6-jgrj

rfc3161-client Has Improper Certificate Validation

CVSS 6.2 MediumEPSS 0.0019 · 9th percentile

Published by the GitHub Advisory Database at 8 Apr 2026, 15:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
rfc3161-clientPyPI<1.0.61.0.6
Identifiers
GHSA-3xxc-pwj6-jgrj · CVE-2026-33753 · PYSEC-2026-3051
Weakness (CWE)
CWE-295
Published
8 Apr 2026
Updated
13 Jul 2026

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.

Written 6 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 15:01 UTC First seen by agentprime
  2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.