CVE-2026-128030 OpenMage magento-lts before 20.18.2 Insufficient Session Expiration After API User Deactivation

7.4 highEPSS 0.4%

High (7.4) in openmage magento-lts. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Affected
Versions
History
References
Your exposure

OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration vulnerability because Mage_Api_Model_Session::_renewBySessId() never checks api_user.is_active and REST OAuth authorization never checks whether the admin user is active. Attackers holding an existing SOAP/XML-RPC session or OAuth access token retain API access after deactivation or API key rotation, reading and modifying customer, order and catalog data.

Severity

CVSS 4.0

7.4 high

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.9 medium

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

EPSS: 0.4% estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE: CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10: A07:2025 Authentication Failures
Published: 2026-11-13 10:18 UTC
Modified: 2026-11-13 15:45 UTC
Assigned by: VulnCheck (CNA)
NVD analysis: Deferred: the NVD does not plan to analyze it
Record from: the NVD, synced 2026-11-13 16:08 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-128030 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128030?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128030?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128030 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-128030](https://cve.bz/cve/badge/CVE-2026-128030.svg)](https://cve.bz/cve/CVE-2026-128030)

HTML:

<a href="https://cve.bz/cve/CVE-2026-128030"><img src="https://cve.bz/cve/badge/CVE-2026-128030.svg" alt="CVE-2026-128030"></a>

Affected

openmage:magento-lts

Versions

From the CNA's record in the CVE List.

Product	Affected
OpenMage magento-lts	before 20.18.2
OpenMage magento-lts	from 21.0.0-beta1 before 21.0.0-beta3

History

2026-11-13 The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stack JSON