# CVE-2022-26205: Code injection in n/a

> Attackers can execute arbitrary code in the Marky library by injecting crafted payloads into display text fields.

- **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:** No
- **Published:** 27 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8cgg-97vc-pp86

## What is CVE-2022-26205?

CVE-2022-26205 is a critical code injection vulnerability in n/a, published on 27 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Marky commit 3686565726c65756e was discovered to contain a remote code execution (RCE) vulnerability via the Display text fields. This vulnerability allows attackers to execute arbitrary code via injection of a crafted payload.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Marky Project Marky.

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

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

## Is CVE-2022-26205 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26205 is a critical code injection vulnerability in n/a, published on 27 Mar 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-26205 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-26205/ (Markdown: https://insights.sbomify.com/CVE-2022-26205/index.md)
```

## Sources

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

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