CVE-2026-56304

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-06-20. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

picklescan before 1.0.1 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attackers to create arbitrary zero-byte files via logging.FileHandler class instantiation. Attackers can exploit this by crafting malicious pickle payloads to bypass RCE blocklists and create lock files or other filesystem artifacts, potentially causing denial of service or application disruption.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 20, 2026

Last Modified

June 24, 2026

Advisory Details (2)

Auto-updated Jun 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

picklescan - Arbitrary File Creation via logging.FileHandler Deserialization | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-arbitrary-file-creation-via-logging-filehandler-deserialization
github Patch Available🟡 PoC Available

Arbitrary file create using logging.FileHandler · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-m7j5-r2p5-c39r

Vendor Advisories for CVE-2026-56304(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
picklescan0.0.1 ... 1.0.0 (36 versions)1.0.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 178 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:11 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-13 12:58 UTCEG score recompute
  8. 2026-09-13 12:58 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 20:44 UTCEG score recompute
  19. 2026-08-30 20:44 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 03:10 UTCEG score recompute
  2. 2026-08-25 03:10 UTCGHSA enrichment
  3. 2026-08-24 01:08 UTCEG score recompute
  4. 2026-08-24 01:08 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 23:02 UTCEG score recompute
  7. 2026-08-22 23:02 UTCGHSA enrichment
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 09:48 UTCEG score recompute
  10. 2026-08-21 09:48 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 07:55 UTCEG score recompute
  13. 2026-08-20 07:55 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 05:49 UTCEG score recompute
  16. 2026-08-19 05:49 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 15:31 UTCEG score recompute
  19. 2026-08-17 15:31 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 13:38 UTCEG score recompute
  23. 2026-08-16 13:38 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 11:36 UTCEG score recompute
  26. 2026-08-15 11:36 UTCGHSA enrichment
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-14 09:42 UTCEG score recompute
  29. 2026-08-14 09:42 UTCGHSA enrichment
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-13 07:49 UTCEG score recompute
  32. 2026-08-13 07:49 UTCGHSA enrichment
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-12 05:26 UTCEG score recompute
  35. 2026-08-12 05:26 UTCGHSA enrichment
  36. 2026-08-11 03:33 UTCEG score recompute
  37. 2026-08-11 03:33 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 01:39 UTCEG score recompute
  40. 2026-08-10 01:39 UTCGHSA enrichment
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-08 23:46 UTCEG score recompute
  43. 2026-08-08 23:46 UTCGHSA enrichment
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-07 21:52 UTCEG score recompute
  46. 2026-08-07 21:52 UTCGHSA enrichment
  47. 2026-08-06 19:59 UTCEG score recompute
  48. 2026-08-06 19:59 UTCGHSA enrichment
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-05 18:05 UTCGHSA enrichment
  52. 2026-08-04 16:12 UTCEG score recompute
  53. 2026-08-04 16:12 UTCGHSA enrichment
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:39 UTCEPSS rescore
  56. 2026-08-03 14:19 UTCEG score recompute
  57. 2026-08-03 14:19 UTCGHSA enrichment
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-02 09:44 UTCEG score recompute
  60. 2026-08-02 09:43 UTCGHSA enrichment
  61. 2026-08-02 02:27 UTCEPSS rescore
  62. 2026-08-01 07:50 UTCEG score recompute
  63. 2026-08-01 07:50 UTCGHSA enrichment
  64. 2026-08-01 04:16 UTCEPSS rescore
  65. 2026-07-31 05:23 UTCEG score recompute
  66. 2026-07-31 05:23 UTCGHSA enrichment
  67. 2026-07-30 16:28 UTCEPSS rescore
  68. 2026-07-30 03:29 UTCEG score recompute
  69. 2026-07-30 03:29 UTCGHSA enrichment
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-30 01:30 UTCEPSS rescore
  72. 2026-07-29 01:32 UTCEG score recompute
  73. 2026-07-29 01:31 UTCGHSA enrichment
  74. 2026-07-28 15:37 UTCEPSS rescore
  75. 2026-07-27 18:26 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-56304?
CVE-2026-56304 is a medium vulnerability published on June 20, 2026. picklescan before 1.0.1 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attackers to create arbitrary zero-byte files via logging.FileHandler class instantiation. Attackers can exploit this by crafting malicious pickle payloads to bypass RCE blocklists and create…
When was CVE-2026-56304 disclosed?
CVE-2026-56304 was first published in the National Vulnerability Database on June 20, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56304 actively exploited?
CVE-2026-56304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.1% of all scored CVEs.
What is the CVSS score of CVE-2026-56304?
CVE-2026-56304 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-56304?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56304, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56304

Explore →

Is Your Infrastructure Affected by CVE-2026-56304?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs