Skip to main content
VulnerabilityPublished Updated

CVE-2025-52556: Sigstore · rfc3161-client has insufficient verification for timestamp response signatures

Affects sigstoreSource GCVE Database

0
Compare
Authoritative record:CVE-2025-52556· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.6.3_3 as a priority.

Data as of 17 Nov 2026, 17:34 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.6.3_3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade sigstore to 3.6.3_3.

Affected software

ProductAffectedFixed in
Homebrewsigstorepkg:brew/sigstoreOther threatsAffected
  • >=3.6.0 <3.6.3_3
Fixed in
  • 3.6.3_3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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

References

Community reviews

Loading reviews…