Amazon Deep Java Library Arbitrary File Read Vulnerability
Is it fixed? Not yet.
Ongoing since Nov 16, 19:17 UTC. First reported Nov 16, 19:17 UTC. Not on the vendor’s status page yet.
What happened
An external control of a file path vulnerability (CVE-2026-129266) exists in Amazon Deep Java Library (DJL) versions 0.7.0 through 0.38.0, potentially allowing remote unauthenticated third parties to read arbitrary files via crafted model archives. Users should upgrade to version 0.39.0 or later to remediate the issue.
What caused it?
External control of a file path in the library allows reading arbitrary files accessible by the process when a crafted model archive is supplied.
Source: tenable.com
Workaround available
Upgrade to version 0.39.0 or later.
Official fixTimeline
- Investigating(done)
- Workaround available(current)
- Resolved(upcoming)
- First report on security advisory
External control of a file path in Amazon Deep Java Library (DJL): CVE-2026-129266 (High)
Source - Workaround discovered
Workaround reported: Upgrade to version 0.39.0 or later.
Source - Status changed
Status changed: new → workaround_available (workaround reported in source signals).
Evidence
1 report · 1 CVEShow
- [1]CVE First reportExternal control of a file path in Amazon Deep Java Library (DJL): CVE-2026-129266 (High)(opens security advisory in a new tab)
High severity. External control of a file path in Amazon Deep Java Library (DJL) versions 0.7.0 through 0.38.0 might allow a remote unauthenticated third party to read arbitrary files that the library process can access. To do this, the third party supplies a crafted model archive. To remediate this issue, users should upgrade to version 0.39.0 or later.
by Tenable 0upvotes 0comments
FAQ
What happened in the AWS issue?
An external control of a file path vulnerability (CVE-2026-129266) exists in Amazon Deep Java Library (DJL) versions 0.7.0 through 0.38.0, potentially allowing remote unauthenticated third parties to read arbitrary files via crafted model archives. Users should upgrade to version 0.39.0 or later to remediate the issue.
What is affected by the AWS issue?
AWS (versions: 0.7.0 through 0.38.0).
When did the AWS issue start and end?
It started Nov 16, 19:17 UTC and is still ongoing (2 d 8 h so far). This page updates as it develops.
How do I get alerts for AWS?
Subscribe to the AWS RSS feed for every new AWS incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether AWS is down. AWS feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.