CVE-2026-16218

LOWPre-NVD 2.62.6—
EchelonGraph scoreMEDIUM confidence

Score 2.6 from GitHub Security Advisory (severity: LOW) published 2026-07-19. a secondary CVSS source baseline 2.6; sources differ by 0.0.

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

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

A vulnerability was detected in hunvreus devpush up to 0.4.6. Affected by this issue is the function reset_storage of the file app/workers/tasks/storage.py of the component Storage Reset Failure Handler. The manipulation results in improper check or handling of exceptional conditions. A high complexity level is associated with this attack. The exploitation is known to be difficult. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
2.6
EG Score
2.6(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity26% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

References (7)

Vendor Advisories for CVE-2026-16218(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 20:24 UTCEG score recompute
  8. 2026-09-05 20:24 UTCGHSA enrichment
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 13:53 UTCEPSS rescore
  12. 2026-09-01 04:39 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 16:45 UTCEG score recompute
  15. 2026-08-30 16:45 UTCGHSA enrichment
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 12:01 UTCEG score recompute
  20. 2026-08-27 12:01 UTCGHSA enrichment
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 06:41 UTCEG score recompute
  24. 2026-08-24 06:41 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 55 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 01:57 UTCEG score recompute
  3. 2026-08-21 01:57 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 21:11 UTCEG score recompute
  8. 2026-08-17 21:11 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 15:35 UTCEG score recompute
  14. 2026-08-14 15:35 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-11 10:51 UTCEG score recompute
  19. 2026-08-11 10:51 UTCGHSA enrichment
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 06:08 UTCEG score recompute
  24. 2026-08-08 06:08 UTCGHSA enrichment
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 01:24 UTCEG score recompute
  28. 2026-08-05 01:24 UTCGHSA enrichment
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:38 UTCEPSS rescore
  31. 2026-08-03 10:35 UTCEPSS rescore
  32. 2026-08-02 02:26 UTCEPSS rescore
  33. 2026-08-01 20:41 UTCEG score recompute
  34. 2026-08-01 20:41 UTCGHSA enrichment
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-29 15:57 UTCEG score recompute
  37. 2026-07-29 15:57 UTCGHSA enrichment
  38. 2026-07-27 14:13 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 11:14 UTCEG score recompute
  42. 2026-07-26 11:13 UTCGHSA enrichment
  43. 2026-07-25 14:17 UTCEPSS rescore
  44. 2026-07-25 14:17 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:05 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:24 UTCEPSS rescore
  49. 2026-07-20 17:49 UTCEG score recompute
  50. 2026-07-20 17:49 UTCGHSA enrichment
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 14:30 UTCEPSS rescore
  53. 2026-07-19 06:24 UTCEG score recompute
  54. 2026-07-19 05:53 UTCEG score recompute
  55. 2026-07-19 05:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16218?
CVE-2026-16218 is a low vulnerability published on July 19, 2026. A vulnerability was detected in hunvreus devpush up to 0.4.6. Affected by this issue is the function reset_storage of the file app/workers/tasks/storage.py of the component Storage Reset Failure Handler. The manipulation results in improper check or handling of exceptional conditions. A high…
When was CVE-2026-16218 disclosed?
CVE-2026-16218 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16218 actively exploited?
CVE-2026-16218 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 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-16218?
CVE-2026-16218 has a CVSS v3 base score of 2.6 (NVD).
How do I remediate CVE-2026-16218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16218, 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

Explore the affected products and dependency analysis for CVE-2026-16218

Explore →

Is Your Infrastructure Affected by CVE-2026-16218?

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

Start Free Scan →Browse All CVEs