{"answers":{"affected":"3 open source packages ship an affected version, including rfc3161-client.","exploited":"There is no known exploitation of CVE-2025-52556 in the wild and no public exploit code.","fix":"Upgrade rfc3161-client to 1.0.3 or later.","what":"CVE-2025-52556 is a critical vulnerability in trailofbits rfc3161-client, published on 21 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52556 and fix it if it is affected.\n\nWhat it is: CVE-2025-52556 is a critical vulnerability in trailofbits rfc3161-client, published on 21 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52556 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rfc3161-client (PyPI): affected all versions; fixed in 1.0.3\n- rfc3161-client (PyPI): affected all versions; fixed in 1.0.3\n- rfc3161-client (PyPI): affected all versions; fixed in 1.0.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52556/ (Markdown: https://insights.sbomify.com/CVE-2025-52556/index.md)","id":"CVE-2025-52556","markdown":"https://insights.sbomify.com/CVE-2025-52556/index.md","name":"CVE-2025-52556","record":{"aliases":["GHSA-6qhv-4h7r-2g9m","PYSEC-2026-525","openSUSE-SU-2025:15282-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python TSP library","requires_auth":"none","summary":"Attackers can bypass timestamp response signature verification by providing arbitrary signatures, undermining trust in time-stamped data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to version 1.0.3, there is a flaw in the timestamp response signature verification logic. In particular, chain verification is performed 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. This issue has been patched in version 1.0.3. There is no workaround for this issue.","ecosystems":["PyPI","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"rfc3161-client has insufficient verification for timestamp response signatures","id":"CVE-2025-52556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"Mail-0 Zero Session Hijacking Via Email","id":"CVE-2025-52557"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"rfc3161-client","purl":null,"source":"GHSA-6qhv-4h7r-2g9m"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"rfc3161-client","purl":"pkg:pypi/rfc3161-client","source":"GHSA-6qhv-4h7r-2g9m"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"rfc3161-client","purl":"pkg:pypi/rfc3161-client","source":"PYSEC-2026-525"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.0.3-1.1"],"introduced":["0"],"last_affected":[],"package":"python-rfc3161-client","purl":"pkg:rpm/opensuse/python-rfc3161-client\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15282-1"}],"prev":{"headline":"CephFS Permission Escalation Vulnerability in Ceph Fuse mounted FS","id":"CVE-2025-52555"},"products":["rfc3161-client"],"published":"2025-06-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-23","vendors":["trailofbits"]},"summary":"Attackers can bypass timestamp response signature verification by providing arbitrary signatures, undermining trust in time-stamped data.","url":"https://insights.sbomify.com/CVE-2025-52556/"}