OpenWrt Project is a Linux operating system targeting embedded devices. In versions prior to both 24.10.6 and 25.12.1, the jp_get_token function, which performs lexical analysis by breaking input expressions into tokens, contains a memory leak vulnerability when extracting string literals, field labels, and regular expressions using dynamic memory allocation. These extracted results are stored in a jp_opcode struct, which is later copied to a newly allocated jp_opcode object via jp_alloc_op. During this transfer, if a string was previously extracted and stored in the initial jp_opcode, it is copied to the new allocation but the original memory is never freed, resulting in a memory leak. This issue has been fixed in versions 24.10.6 and 25.12.1.
CVE-2026-30873
This medium-severity CVE scores 4.9 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 4.9(low)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity49% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
March 19, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/openwrt/openwrt/releases/tag/v24.10.6
- security-advisories@githubhttps://github.com/openwrt/openwrt/releases/tag/v25.12.1
- security-advisories@githubhttps://github.com/openwrt/openwrt/security/advisories/GHSA-rcc6-v4r6-gj4m
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:38 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-30873?
When was CVE-2026-30873 disclosed?
Is CVE-2026-30873 actively exploited?
What is the CVSS score of CVE-2026-30873?
How do I remediate CVE-2026-30873?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-30873
Is Your Infrastructure Affected by CVE-2026-30873?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.