# CVE-2025-69443: Code injection in n/a

> Attackers can execute arbitrary commands and steal API keys by tricking users into visiting a crafted HTML page in Archon.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-9w6r-hr5j-2g2p

## What is CVE-2025-69443?

CVE-2025-69443 is a medium-severity code injection vulnerability in n/a, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Remote Code Execution in coleam00 Archon 0.1.0. A crafted HTML page, when accessed by a victim, can execute commands, run prompts on behalf of the user, control the Archon UI features, and steal all Archon information available on the UI including API keys.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-69443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69443 is a medium-severity code injection vulnerability in n/a, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-69443 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-2025-69443/ (Markdown: https://insights.sbomify.com/CVE-2025-69443/index.md)
```

## Sources

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

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