{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62381 exists.","fix":"No fix has been published for CVE-2026-62381 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62381 is a medium-severity memory corruption vulnerability in openwrt luci, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62381 and fix it if it is affected.\n\nWhat it is: CVE-2026-62381 is a medium-severity memory corruption vulnerability in openwrt luci, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62381 exists.\n\nAffected product: openwrt luci. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62381/ (Markdown: https://insights.sbomify.com/CVE-2026-62381/index.md)","id":"CVE-2026-62381","markdown":"https://insights.sbomify.com/CVE-2026-62381/index.md","name":"CVE-2026-62381","record":{"aliases":["GHSA-g4fj-xr23-w9hm","GHSA-jgc3-4q3p-g6xh"],"analysis":{"component_type":"operating_system","fix_type":"end_of_life","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenWrt LuCI library","requires_auth":"low_privilege","summary":"Heap buffer overflow in OpenWrt LuCI certificate signing allows potential code execution or denial of service via crafted RSA keys.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"luci-lib-px5g 2040-bit Certificate Signing Heap Buffer Overflow","id":"CVE-2026-62381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"PasswordPusher before v2.9.6 Authentication Bypass via Null Comparison","id":"CVE-2026-62382"},"packages":[],"prev":{"headline":"Netty before 4.2.16.Final SOCKS Proxy Null Byte Injection","id":"CVE-2026-62380"},"products":["luci"],"published":"2026-08-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-24","vendors":["openwrt"]},"summary":"Heap buffer overflow in OpenWrt LuCI certificate signing allows potential code execution or denial of service via crafted RSA keys.","url":"https://insights.sbomify.com/CVE-2026-62381/"}