Summary
LocalS3 CreateBucketConfiguration Endpoint XML External Entity (XXE) Injection
Impact
The vulnerability allows unauthenticated attackers to make the server perform HTTP requests to internal networks and services, potentially exposing sensitive information or enabling further attacks against internal systems. The attacker only needs to be able to send HTTP requests to the LocalS3 service to exploit this vulnerability.
An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-27136? CVE-2025-27136 is a medium-severity XML external entity injection (XXE) vulnerability in io.github.robothy:local-s3-rest (maven), affecting versions < 1.21. It is fixed in 1.21. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
- Which versions of io.github.robothy:local-s3-rest are affected by CVE-2025-27136? io.github.robothy:local-s3-rest (maven) versions < 1.21 is affected.
- Is there a fix for CVE-2025-27136? Yes. CVE-2025-27136 is fixed in 1.21. Upgrade to this version or later.
- Is CVE-2025-27136 exploitable, and should I be worried? Whether CVE-2025-27136 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-27136 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-27136? Upgrade
io.github.robothy:local-s3-restto 1.21 or later.