# CVE-2026-12553: HP Web Jetadmin (WJA) - Potential Arbitrary File Read/Write

> Unauthenticated attackers can read or write arbitrary files via DLL hijacking in HP Web Jetadmin, requiring a patch to mitigate.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-29p9-9rf3-jx84

## What is CVE-2026-12553?

CVE-2026-12553 is a high-severity path traversal vulnerability in HP Inc. Web Jetadmin, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HP has identified a potential vulnerability in HP Web Jetadmin (WJA) that may allow an unauthenticated actor to read from or write to arbitrary files through a DLL hijacking mechanism.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-12553 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12553 is a high-severity path traversal vulnerability in HP Inc. Web Jetadmin, published on 17 Aug 2026. 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-2026-12553 in the wild and no public exploit code.

Affected product: HP Inc. Web Jetadmin. 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-12553/ (Markdown: https://insights.sbomify.com/CVE-2026-12553/index.md)
```

## Sources

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

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