# CVE-2025-56590: Command injection in n/a

> Attackers can execute arbitrary OS commands via the InsertFromURL function in the Apryse HTML2PDF SDK.

- **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:** 22 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-j34c-g9jq-8cr8

## What is CVE-2025-56590?

CVE-2025-56590 is a critical command injection vulnerability in n/a, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the InsertFromURL() function of the Apryse HTML2PDF SDK thru 11.10. This vulnerability could allow an attacker to execute arbitrary operating system commands on the local server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Apryse Html2pdf.

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

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

## Is CVE-2025-56590 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56589](https://insights.sbomify.com/CVE-2025-56589/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56590 is a critical command injection vulnerability in n/a, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56590 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-2025-56590/ (Markdown: https://insights.sbomify.com/CVE-2025-56590/index.md)
```

## Sources

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

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