# CVE-2022-26635: Other in n/a

> Attackers may perform CLRF injection via improper NULL termination in PHP-Memcached, though third parties dispute this vulnerability's validity.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-9342, GHSA-hph6-79wj-qqmw

## What is CVE-2022-26635?

CVE-2022-26635 is a critical vulnerability in n/a, published on 5 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP-Memcached v2.2.0 and below contains an improper NULL termination which allows attackers to execute CLRF injection. Note: Third parties have disputed this as not affecting PHP-Memcached directly.

## Which versions are affected by CVE-2022-26635?

It affects 1 product.


Products: Php Memcached.

## How do I fix CVE-2022-26635?

No fix published yet.

## Is CVE-2022-26635 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26635 and fix it if it is affected.

What it is: CVE-2022-26635 is a critical vulnerability in n/a, published on 5 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26635 in the wild and no public exploit code.

Affected product: n/a. 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-2022-26635/ (Markdown: https://insights.sbomify.com/CVE-2022-26635/index.md)
```

## Sources

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

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