CVE-2026-30873
Received Received - Intake
Memory Leak in OpenWrt jp_get_token Function Causes Resource Exhaustion

Publication date: 2026-03-19

Last updated on: 2026-03-24

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-19
Last Modified
2026-03-24
Generated
2026-06-16
AI Q&A
2026-03-20
EPSS Evaluated
2026-06-14
NVD
CVE-2026-30873
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
openwrt openwrt to 24.10.6 (exc)
openwrt openwrt From 25.12.0 (inc) to 25.12.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-401 The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the OpenWrt Project's jp_get_token function, which is responsible for breaking input expressions into tokens. In versions prior to 24.10.6 and 25.12.1, when extracting string literals, field labels, and regular expressions, the function uses dynamic memory allocation but fails to free the original memory after copying the data to a new jp_opcode object. This results in a memory leak.

Impact Analysis

The memory leak caused by this vulnerability can lead to increased memory usage over time, potentially degrading system performance or causing the device to run out of memory. This can affect the stability and reliability of embedded devices running vulnerable versions of OpenWrt.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade your OpenWrt system to version 24.10.6 or 25.12.1 or later, where the memory leak issue in the jp_get_token function has been fixed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-30873. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart