Rejected as issued in error
Published Oct 14, 2025 · Updated Oct 14, 2025
Adobe Commerce is not affected by CVE-2025-54277 because Adobe rejected the identifier as having been issued in error. No vulnerability mechanism, attacker path, or security impact remains associated with the rejected record. Adobe removed the prior authorization, CVSS, CWE, affected-version, and bulletin-reference assertions, so the former unauthorized-read description does not describe a confirmed vulnerability.
Summary
What happened
Adobe Commerce is not affected by CVE-2025-54277 because Adobe rejected the identifier as having been issued in error. No vulnerability mechanism, attacker path, or security impact remains associated with the rejected record. Adobe removed the prior authorization, CVSS, CWE, affected-version, and bulletin-reference assertions, so the former unauthorized-read description does not describe a confirmed vulnerability.
The record
- CVE
- CVE-2025-54277
- Published
- Oct 14, 2025
- Updated
- Oct 14, 2025
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo