CVE & CISA-KEV Catalog

CVE-2026-62381

MEDIUM
6.6
CVSS v3
NVD

Description

luci-lib-px5g (LuCI) contains a heap-based buffer overflow in the native ASN.1 encoding routine asn1_add_obj (x509write.c) when signing a certificate with a 2040-bit RSA key. For a 255-byte signature, the BIT STRING allocation is computed from the DER length encoding of 255 bytes, but the payload written after prepending the unused-bits byte is 256 bytes, requiring one additional DER length octet. As a result the allocation is 259 bytes while the tag, length, unused-bits byte, and signature require 260 bytes, and the final memcpy writes one byte beyond the heap buffer. The overflow is reachable through the exported Lua interface via create_selfsigned(); whether it is remotely exploitable depends on the embedding application. The vulnerable code is present on the openwrt-18.06 through openwrt-25.12 release branches and is absent from master, where the luci-lib-px5g package has been removed rather than patched.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityLow
IntegrityLow
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

Exploit Intelligence

0.08%probability of exploitation in 30 days
0thpercentile

Low risk: more likely to be exploited than 0% of all known CVEs.

References

Other references2

Related Vulnerabilities

Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2015-3113Critical9.8100%KEVFix
CVE-2024-26256High7.888%-Fix
CVE-2020-25687Medium5.987%-Fix
CVE-2009-3459High8.887%KEVFix
CVE-2021-21017High8.886%KEV-
CVE-2020-25683Medium5.986%-Fix

Common questions

How do I fix CVE-2026-62381?

No published fix for CVE-2026-62381 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-62381 being actively exploited?

Not that we know of. CVE-2026-62381 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.08% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.

How severe is CVE-2026-62381?

CVE-2026-62381 has a CVSS v3 base score of 6.6, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-62381
CVE-2026-62381 severity badge

Markdown

[![CVE-2026-62381](https://tridentstack.com/cve/badge/CVE-2026-62381.svg)](https://tridentstack.com/cve/CVE-2026-62381)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-62381"><img src="https://tridentstack.com/cve/badge/CVE-2026-62381.svg" alt="CVE-2026-62381"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-24.