CVE-2026-129266

waiting for further signalsZero needs more public information before it can validate it.

GHSA-xf3w-qp3m-fp62 ↗EUVD-2026-126614 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Amazon djl >= 0.7.0, <= 0.39.0
fixed in 0.40.0
CWE-73 External Control of File Name or Path
ETK-2026-4610Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:maven/ai.djl/api
2d 02h 56msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h36m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Amazon DJL versions 0.7.0 through 0.38.0 may allow unauthenticated remote attackers to read files accessible to the library process. Exposure requires an attacker to be able to provide a model archive for processing.

mitigation

Upgrade DJL to version 0.39.0 or later. Until upgraded, restrict untrusted parties from supplying model archives and limit the DJL process's file permissions.

fixed in 0.40.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.52%44th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-16 18:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-16 18:33Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-129266

{
  "etk_id": "ETK-2026-4610",
  "cve_id": "CVE-2026-129266",
  "display_id": "CVE-2026-129266",
  "ghsa_id": "GHSA-xf3w-qp3m-fp62",
  "euvd_id": "EUVD-2026-126614",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file read via model archives in Amazon DJL",
  "summary": "Amazon DJL versions 0.7.0 through 0.38.0 may allow unauthenticated remote attackers to read files accessible to the library process. Exposure requires an attacker to be able to provide a model archive for processing.",
  "mitigation": "Upgrade DJL to version 0.39.0 or later. Until upgraded, restrict untrusted parties from supplying model archives and limit the DJL process's file permissions.",
  "vendor": "Amazon",
  "product": "djl",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.7.0, <= 0.39.0"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "0.40.0"
      ],
      "package_name": "ai.djl:api",
      "purl": "pkg:maven/ai.djl/api"
    }
  ],
  "cwes": [
    73
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0052,
  "epss_percentile": 0.4469,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.121369416666667,
  "t0_at": "2026-11-16T18:33:52.192000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-16T18:33:52.192000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-16T18:33:52.192000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-129266"
    }
  }
}

published 2026-11-16 18:59Z
last change 2026-11-18 21:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.