# CVE-2026-24311: Insecure Storage Protection vulnerability in SAP Customer Checkout 2.0

> Attackers can read and modify locally stored operational data in SAP Customer Checkout due to reversible protection mechanisms, compromising confidentiality and integrity.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-j8g4-mcwm-v999

## What is CVE-2026-24311?

CVE-2026-24311 is a medium-severity vulnerability in SAP_SE SAP Customer Checkout 2.0, published on 10 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The SAP Customer Checkout application exhibits certain design characteristics that involve locally storing operational data using reversible protection mechanisms. Access to this data, combined with user?initiated interaction, may allow modifications to occur without validation. Such changes could affect system behaviour during startup, resulting in a high impact on the application's confidentiality and integrity, with a low impact on availability.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-24311?


## How do I fix CVE-2026-24311?

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

## Is CVE-2026-24311 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24311 and fix it if it is affected.

What it is: CVE-2026-24311 is a medium-severity vulnerability in SAP_SE SAP Customer Checkout 2.0, published on 10 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-24311 in the wild and no public exploit code.

Affected product: SAP_SE SAP Customer Checkout 2.0. 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-2026-24311/ (Markdown: https://insights.sbomify.com/CVE-2026-24311/index.md)
```

## Sources

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

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