Is fickling affected by GHSA-wccx-j62j-r448?

PyPI fickling is affected in <0.1.9.

Is GHSA-wccx-j62j-r448 being exploited?

Not on the CISA KEV list. EPSS exploit probability is not available.

high

GHSA-wccx-j62j-r448

Q: Is GHSA-wccx-j62j-r448 being exploited?

Not on the CISA KEV list. EPSS exploit probability is not available.

PyPI · fickling

Summary

Fickling has `always_check_safety()` bypass: pickle.loads and _pickle.loads remain unhooked

Severity: high
Published: 2026-03-04

References

https://github.com/trailofbits/fickling/security/advisories/GHSA-wccx-j62j-r448
https://github.com/trailofbits/fickling/commit/8c24c6edabceab156cfd41f4d70b650e1cdad1f7
https://github.com/trailofbits/fickling

Related advisories

GHSA-5hwf-rc88-82xm — high · PyPI/fickling
GHSA-mxhj-88fx-4pcv — high · PyPI/fickling
CVE-2026-22612 — high · PyPI/fickling
CVE-2026-22609 — high · PyPI/fickling
CVE-2026-22608 — high · PyPI/fickling
CVE-2026-22607 — high · PyPI/fickling
CVE-2026-22606 — high · PyPI/fickling
CVE-2025-67748 — high · PyPI/fickling

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.