Armeria: External Control of File Name or Path in xDS SDS DataSource

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2026-11752: 0.32% estimated exploitation activity in the next 30 days; percentile 24.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

External Control of File Name or Path in xDS SDS DataSource Summary DataSourceStream in the :xds module resolves control-plane-supplied filename and environmentvariable fields from SDS Secret resources without any allow-list or base-directory confinement. A semi-trusted or compromised xDS control plane (or an attacker who can MITM SDS responses) can read arbitrary local files and environment variables on the xDS client host. Affected component: xds/src/main/java/com/linecorp/armeria/xds/DataSourceStream.java Introduced in: Armeria 1.38.0 (commit b199560b10, "Add support for SDS", #6597) Affected versions: 1.38.0, 1.39.0 Impact A semi-trusted or compromised xDS control plane (or an attacker who can inject/MITM SDS responses) can: - Read arbitrary files on the xDS client host — TLS private keys, /etc/passwd, mounted Kubernetes service-account tokens, cloud credential files, etc. - Read arbitrary environment variables — AWSSECRETACCESSKEY, CI tokens, database credentials, etc. The read…

Published by the source

18 Jun 2026, 17:22 UTC

Last modified by the source

15 Jul 2026, 21:51 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hgw6-8c77-v4gq

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

# Patch Next advisory brief: CVE-2026-11752

Advisory: Armeria: External Control of File Name or Path in xDS SDS DataSource
IDs: CVE-2026-11752, GHSA-hgw6-8c77-v4gq
Record: https://patchnext.com/advisories/cve-2026-11752 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.linecorp.armeria:armeria-xds 1.40.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.linecorp.armeria:armeria-xds: affected < 1.40.0; fixed in 1.40.0

## Suggested inspection (read-only)
- Maven com.linecorp.armeria:armeria-xds: 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 com.linecorp.armeria:armeria-xds.
- 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-hgw6-8c77-v4gq (GitHub-reviewed advisory GHSA-hgw6-8c77-v4gq lists affected ranges: Maven com.linecorp.armeria:armeria-xds >=0 <1.40.0)

Commands are suggestions: review each one before running it.