# CVE-2026-51385: Code injection in n/a

> Remote attackers can execute arbitrary code in GRAPHIFY via unsafe URL handling functions, requiring an upgrade to secure versions.

- **Severity:** Medium 6.9 (`CVSS:3.1/AC:H/AV:N/A:N/C:H/I:L/PR:N/S:C/UI:R`)
- **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:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-xhp5-xjxr-p7vr

## What is CVE-2026-51385?

CVE-2026-51385 is a medium-severity code injection vulnerability in n/a, published on 20 Jul 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

An issue in safishamsi Open-Source GRAPHIFY v.0.3.2 through v0.4.29 allows a remote attacker to execute arbitrary code via the validate_url, safe_fetch, _build_opener, _fetch_html and _download_binary functions.

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

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


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

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

## Is CVE-2026-51385 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51385 exists.

Public exploit code:

- Advisory for CVE-2026-51385. Needed to publish it as GRAPHIFY hasnt recognized the advisory neither publish it, and MITRE assigned CVE-2026-51385, this is the advisory for it. (github_poc): https://github.com/Arturo0x90/CVE-2026-51385

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51385 is a medium-severity code injection vulnerability in n/a, published on 20 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51385 exists.

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

## Sources

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

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