CVE-2026-3490

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-17. a secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 10.0Exploit: NoneExposed: 0

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

picklescan before 1.0.4 fails to block pkgutil.resolve_name, allowing attackers to bypass the entire blocklist by resolving any dangerous function through indirect REDUCE calls. Remote attackers can invoke any blocked function such as os.system, builtins.exec, or subprocess.call to achieve remote code execution.

CVSS v3
10.0
EG Score
10.0(high)
EPSS
45.6%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 18, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

pkgutil.resolve_name universal blocklist bypass · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-vvpj-8cmc-gx39
generic

picklescan - Universal Blocklist Bypass via pkgutil.resolve_name | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-universal-blocklist-bypass-via-pkgutil-resolve-name

Vendor Advisories for CVE-2026-3490(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.3 (39 versions)1.0.4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 52× in last 7d / 169× 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 169 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-3490?
CVE-2026-3490 is a critical vulnerability published on June 17, 2026. picklescan before 1.0.4 fails to block pkgutil.resolve_name, allowing attackers to bypass the entire blocklist by resolving any dangerous function through indirect REDUCE calls. Remote attackers can invoke any blocked function such as os.system, builtins.exec, or subprocess.call to achieve remote…
When was CVE-2026-3490 disclosed?
CVE-2026-3490 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3490 actively exploited?
CVE-2026-3490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3490?
CVE-2026-3490 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-3490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3490, 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-3490

Explore →

Is Your Infrastructure Affected by CVE-2026-3490?

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