GHSA-xf3w-qp3m-fp62 · Package
NO FIX YET · SEE WHAT TO DO
Deep Java Library (DJL) does not validate the resource location in model archive metadata. A remote unauthenticated attacker who supplies a crafted model archive can read any file the library process can access.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that load model archives in DJL, including djl-serving and the djl-inference Deep Learning Container. Exposure is greatest where the management or inference APIs accept model registration from untrusted callers. Teams that only load trusted, locally built models are less exposed but should still upgrade.
Not affected if apis-not-exposed, trusted-models-only, versions-outside-range
Who cares aws, deep-learning, djl-serving, java, lab-disclosure, model-serving
>=0.7.0, <=0.38.0.model_url_pattern is set.0.39.0 or later.CVE-2026-129266 - Arbitrary Local File Read in DJL - AWS
Bulletin ID: 2026-183-AWS Scope: AWS/Amazon Content Type: Important (requires attention)/Informational Publication Date: 11/16/2026 10:30 AM PST
Description:
Deep Java Library (DJL) is an open-source, engine-agnostic Java framework for deep learning. We identified CVE-2026-129266, an issue where DJL doesn't validate the resource location specified in model archive metadata. A remote unauthenticated third party could use a crafted model archive to read arbitrary files that the library process can access.
Impacted versions: >=0.7.0, <=0.38.0
Resolution:
This issue has been addressed in DJL version 0.39.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds:
Only load model archives from sources you trust. If you run djl-serving, or a container image that bundles it such as the djl-inference Deep Learning Container, restrict network access to the management and inference APIs so that untrusted callers cannot register models, and set model_url_pattern to an allowlist of model locations you control to restrict models loaded through inference requests.
References:
Acknowledgement:
We would like to thank Oguzhan Akkaya for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email aws-security@amazon.com with any s ecurity questions or concerns.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.