---
id: "CVE-2025-52556"
page: "https://infrastack.ai/live/CVE-2025-52556"
kind: "vulnerability"
aliases: ["CVE-2025-52556", "GHSA-6qhv-4h7r-2g9m"]
title: "rfc3161-client has insufficient verification for timestamp response signatures"
severity: "critical"
cvss: 9.3
epss: 0.00169
exploited: false
status: "open"
category: "package"
products: [{"name": "rfc3161-client", "fixed": ["1.0.3"], "affected": "<= 1.0.2", "ecosystem": "pypi"}]
ecosystems: ["pypi"]
tags: ["cwe-347", "package", "python", "rfc3161", "timestamping"]
not_affected_if: ["no-timestamp-verification", "not-using-rfc3161-client"]
published_at: "2025-06-20T18:08:40+00:00"
first_seen_at: "2026-11-16T16:23:45+00:00"
updated_at: "2026-11-16T16:38:06+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-6qhv-4h7r-2g9m", "first_seen_at": "2026-11-16T16:23:45+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52556", "first_seen_at": "2026-11-16T16:38:06+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00169, "url": "https://api.first.org/data/v1/epss?cve=CVE-2025-52556"}]
---

# rfc3161-client has insufficient verification for timestamp response signatures

Link for people: https://infrastack.ai/live/CVE-2025-52556 (this .md is for agents)

rfc3161-client 1.0.2 and earlier check that a timestamp response's embedded certificate chains to a trusted root but never check the response's own signature. An attacker can therefore present any signature under a valid-looking leaf certificate and have the timestamp treated as verified.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- pypi:rfc3161-client affected <= 1.0.2 fixed 1.0.3

## How to check

- Find the installed version with `pip show rfc3161-client` or check the lock file for `rfc3161-client`.
- Look for any code that calls the library to verify RFC 3161 timestamp responses (TSR).

## Fix

- `rfc3161-client` `1.0.3` or later.

## Timeline

- 2026-11-16T16:23:45+00:00 ghsa https://github.com/advisories/GHSA-6qhv-4h7r-2g9m
- 2026-11-16T16:38:06+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-52556

## Documents

- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/trailofbits/rfc3161-client/security-advisories/GHSA-6qhv-4h7r-2g9m
- [advisory] Maintainer's advisory: github.com https://github.com/trailofbits/rfc3161-client/security/advisories/GHSA-6qhv-4h7r-2g9m
- [fix] Patch: github.com https://github.com/trailofbits/rfc3161-client/commit/724a184f953e3f171f85cb223871172b41b0d0dc

## From the sources

### 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
