LocalS3 Project Bucket Operations Vulnerable to XML External Entity (XXE) Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Description The LocalS3 project contains an XML External Entity (XXE) Injection vulnerability in its bucket operations that process XML data. Specifically, the vulnerability exists in the bucket ACL and bucket tagging operations. The application processes XML input without properly disabling external entity resolution, allowing an attacker to read arbitrary files from the server's filesystem. The vulnerability occurs because the XML parser used by the application processes DOCTYPE declarations and allows external entity references. When processing bucket ACL or tagging operations, the application includes the content of external entities in its response, effectively exposing sensitive files from the server. This type of vulnerability can be exploited to read sensitive files, perform server-side request forgery (SSRF), or potentially achieve denial of service through various XXE attack vectors. Steps to Reproduce 1. Create a test bucket using PUT request to…

Published by the source

10 Mar 2025, 18:29 UTC

Last modified by the source

10 Mar 2025, 18:29 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2466-4485-4pxj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2466-4485-4pxj

Advisory: LocalS3 Project Bucket Operations Vulnerable to XML External Entity (XXE) Injection
IDs: GHSA-2466-4485-4pxj
Record: https://patchnext.com/advisories/ghsa-2466-4485-4pxj (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.github.robothy:local-s3-rest 1.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.github.robothy:local-s3-rest: affected < 1.21; fixed in 1.21

## Suggested inspection (read-only)
- Maven io.github.robothy:local-s3-rest: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.github.robothy:local-s3-rest.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2466-4485-4pxj (GitHub-reviewed advisory GHSA-2466-4485-4pxj lists affected ranges: Maven io.github.robothy:local-s3-rest >=0 <1.21)

Commands are suggestions: review each one before running it.