Vulnerability in janet-lang janet (CVE-2026-10268)
Summary
Vulnerability in janet-lang janet (CVE-2026-10268). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A weakness has been identified in janet-lang janet up to 1.41.0. This vulnerability affects the function unmarshal_one_fiber of the file src/core/marsh.c. Executing a manipulation can lead to integer overflow. It is possible to launch the attack on the local host. The exploit has been made available to the public and could be used for attacks. This patch is called d9b1d711ea1fde52ac73a82088b512a3e17bad0d. A patch should be applied to remediate this issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10268 has been found in janet-lang janet.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "janet-lang janet CVE-2026-10268" on the vendor's site.
CVE-2026-10268 (janet-lang janet) — CWE-189 / CVSS v3 3.3
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-189) exists in janet-lang janet.
Check the vendor advisory for the affected versions of janet-lang janet.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで janet-lang janet を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- report github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com
- web github.com