NVD / CVE Program· CNA adobe

CVE-2026-48001: Adobe Commerce | Information Exposure (CWE-200)

LowCVSS 3.7 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 14/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Adobe Commerce is affected by an Information Exposure vulnerability that could lead to a limited disclosure of sensitive information. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.

Published: Jul 14, 2026
Updated: Aug 27, 2026
EPSS: 0.5% · 43th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · adobe: 3.7; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
adobe	commerce	cpe:2.3:a:adobe:commerce
adobe	commerce b2b	cpe:2.3:a:adobe:commerce_b2b
adobe	magento	cpe:2.3:a:adobe:magento
adobe	i\/o events	cpe:2.3:a:adobe:i\/o_events

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

Adobe Adobe Commerce
- 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul, 2.4.5-2026-jul, 2.4.4-2026-julnot affected
- up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18affected
Adobe Adobe Commerce B2B
- 1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-julnot affected
- up to and including 1.5.3, 1.5.2-p5, 1.4.2-p10, 1.3.4-p17, 1.3.3-p18affected
Adobe Adobe Commerce Events
- 1.21.0not affected
- up to and including 1.20.0affected · semver
Adobe Magento Open Source
- 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-julnot affected
- up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15affected

Affected versions · NVD (16)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

adobe commerce2.4.4
adobe commerce2.4.5
adobe commerce2.4.6
adobe commerce2.4.7
adobe commerce2.4.8
adobe commerce2.4.9
adobe commerce b2b1.3.3
adobe commerce b2b1.3.4
adobe commerce b2b1.4.2
adobe commerce b2b1.5.2
adobe commerce b2b1.5.3
adobe i/o events1.6.0 and later · before 1.21.0
adobe magento2.4.6
adobe magento2.4.7
adobe magento2.4.8
adobe magento2.4.9

Same product

adobe: all records

Other highest-scoring records for the same primary product.

CVE-2026-75650Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)KEV
100Now
CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV
99Now
CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV
99Now

Published before and after this one in the same product

← EarlierCVE-2026-47999Jul 14, 2026 · Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
19Monitor
← EarlierCVE-2026-48000Jul 14, 2026 · Adobe Commerce | URL Redirection to Untrusted Site ('Open Redirect') (CWE-601)
24Monitor
Later →CVE-2026-48358Jul 14, 2026 · Adobe Commerce | Improper Encoding or Escaping of Output (CWE-116)
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-24408518 days apartAdobe Commerce | Information Exposure (CWE-200)
26Monitor

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

helpx.adobe.com/security/products/magento/apsb26-73.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records