CVE-2026-46378

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.2Exploit: NoneExposed: 0

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

Dasel is a command-line tool and library for querying, modifying, and transforming data structures. From 3.0.0 until 3.10.1, the selector lexer matchRegexPattern closure in (*Tokenizer).parseCurRune in selector/lexer/tokenize.go loops while tokenizing an unterminated regex literal such as r/ because peekRuneEqual returns false after the end of input, allowing attacker-controlled selector strings to consume CPU indefinitely. This issue is fixed in version 3.10.1.

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.6%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 17, 2026

Advisory Details (1)

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

Denial of service in dasel selector lexer due to infinite loop on unterminated regex literal · Advisory · TomWright/dasel · GitHub

https://github.com/TomWright/dasel/security/advisories/GHSA-m6xr-fvfg-5g64

Vendor Advisories for CVE-2026-46378(1)

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

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/tomwright/dasel
github.com/tomwright/dasel/v2
github.com/tomwright/dasel/v33.10.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 10× 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-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 03:17 UTCEG score recompute 1.30
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 23:29 UTCOSV refresh
  10. 2026-07-16 18:18 UTCMITRE cvelistV5CVSS v3 → 6.2 · severity → MEDIUM
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-05-24 06:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46378?
CVE-2026-46378 is a medium vulnerability published on May 19, 2026. Dasel is a command-line tool and library for querying, modifying, and transforming data structures. From 3.0.0 until 3.10.1, the selector lexer matchRegexPattern closure in (*Tokenizer).parseCurRune in selector/lexer/tokenize.go loops while tokenizing an unterminated regex literal such as r/…
When was CVE-2026-46378 disclosed?
CVE-2026-46378 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46378 actively exploited?
CVE-2026-46378 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46378?
CVE-2026-46378 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-46378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46378, 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-46378

Explore →

Is Your Infrastructure Affected by CVE-2026-46378?

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