# CVE-2026-25523: magento-lts — Fixed in 20.16.1

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

# CVE-2026-25523 — magento-lts

MEDIUM 

CVE-2026-25523 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in openmage/magento-lts. A fix is available for openmage/magento-lts — see the affected versions and patch details below.

Magento's X-Original-Url header can expose admin url

Also known as[GHSA-jg68-vhv3-9r8f](/vulnerability/GHSA-jg68-vhv3-9r8f)

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25523.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

0.00%0.30%0.59%0.89%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

1 pkg affected

🐘`openmage/magento-lts`

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

## Description

#### Impact

The admin url can be discovered without prior knowledge of it's location by exploiting the X-Original-Url header on some configurations.

#### Patches

The bug comes from the Zend library and is patche by unsetting the header in the bootstrap process.

#### Workarounds

Unset the `X-Original-Url` header in the web server configuration.

#### References

The activation of these headers is coming from the Zend\_Controller module. It appears this has been known to some degree since 2016 - [https://peterocallaghan.co.uk/2016/12/magento-poisoning-cache/](https://peterocallaghan.co.uk/2016/12/magento-poisoning-cache/) (dead link now..)

#### Credit

Anees Hyder ( @anees0xdev ) via HackerOne [https://hackerone.com/anees0x\_dev/hacktivity](https://hackerone.com/anees0x_dev/hacktivity)

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

🐘Packagist

`openmage/magento-lts` 

all versions

20.16.1`composer require openmage/magento-lts:^20.16.1`

## Affected Products

1 product · 1 configurations

Application

`magento`openmage

≤ 20.16.0

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update openmage/magento-lts to 20.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25523 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
    

## Frequently Asked Questions

\### Impact The admin url can be discovered without prior knowledge of it's location by exploiting the X-Original-Url header on some configurations. ### Patches The bug comes from the Zend library and is patche by unsetting the header in the bootstrap process. ### Workarounds Unset the \`X-Original-Url\` header in the web server configuration. ### References The activation of these headers is coming from the Zend\_Controller module. It appears this has been known to some degree since 2016 - https://peterocallaghan.co.uk/2016/12/magento-poisoning-cache/ (dead link now..) ### Credit Anees H

O3 Security · Impact-Aware SCA

### Is CVE-2026-25523 in your dependencies?

Find it across Packagist, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)