# CVE-2025-26654: Potential information disclosure vulnerability in SAP Commerce Cloud (Public Cloud)

> Attackers can intercept confidential data sent over unencrypted HTTP before the redirect to HTTPS occurs, impacting data confidentiality.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-gj2r-xj7g-vp59

## What is CVE-2025-26654?

CVE-2025-26654 is a medium-severity vulnerability in SAP_SE SAP Commerce Cloud (Public Cloud), published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP Commerce Cloud (Public Cloud) does not allow to disable unencrypted HTTP (port 80) entirely, but instead allows a redirect from port 80 to 443 (HTTPS). As a result, Commerce normally communicates securely over HTTPS. However, the confidentiality and integrity of data sent on the first request before the redirect may be impacted if the client is configured to use HTTP and sends confidential data on the first request before the redirect.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2025-26654?


## How do I fix CVE-2025-26654?

No fix has been published for CVE-2025-26654 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-26654 being exploited?

There is no known exploitation of CVE-2025-26654 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26654 and fix it if it is affected.

What it is: CVE-2025-26654 is a medium-severity vulnerability in SAP_SE SAP Commerce Cloud (Public Cloud), published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26654 in the wild and no public exploit code.

Affected product: SAP_SE SAP Commerce Cloud (Public Cloud). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-26654/ (Markdown: https://insights.sbomify.com/CVE-2025-26654/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26654
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26654
- OSV: https://osv.dev/vulnerability/CVE-2025-26654

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26654/
Summaries are generated and may contain mistakes; the official description above is the record.