# CVE-2026-24402: GitHub cannot issue a CVE for this Security Advisory because this advisory includes information about more than one vulnerability.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Updated:** 24 Jan 2026

## What is CVE-2026-24402?

CVE-2026-24402 is a vulnerability. 

### Official description

GitHub cannot issue a CVE for this Security Advisory because this advisory includes information about more than one vulnerability.

According to [rule 4.2.11 of the CVE CNA rules](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_4-2_CVE_ID_Assignment):

> 4.2.6 CNAs SHOULD assign different CVE IDs to separate Vulnerabilities, as determined using the guidance in [4.1](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_4-1_Vulnerability_Determination).

> 4.2.11 CNAs SHOULD assign different CVE IDs to different, Independently Fixable Vulnerabilities.

You can move forward in one of two ways:

- If you agree that this Security Advisory concerns more than one independently fixable vulnerability, split each vulnerability into its own advisory and request one CVE for each vulnerability.
- If you do not agree that these vulnerabilities are independently fixable, resubmit the CVE request with a section clarifying how they are dependent and should have the same CVE.

Thank you for making the open source ecosystem more secure by fixing and responsibly disclosing these vulnerabilities.

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


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

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

## Is CVE-2026-24402 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24402 is a vulnerability. 
Exploitation: There is no known exploitation of CVE-2026-24402 in the wild and no public exploit code.

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-24402/ (Markdown: https://insights.sbomify.com/CVE-2026-24402/index.md)
```

## Sources

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

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