# CVE-2026-5304: Privilege escalation in AXIS OS

> Attackers can escalate privileges by installing malicious unsigned ACAP applications on Axis devices configured to allow such installations.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-xj6x-54xc-64j5

## What is CVE-2026-5304?

CVE-2026-5304 is a medium-severity vulnerability in AXIS OS, published on 11 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An ACAP configuration file lacks input validation, which could potentially lead to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2026-5304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5304 is a medium-severity vulnerability in AXIS OS, published on 11 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5304 in the wild and no public exploit code.

Affected product: AXIS OS. 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-5304/ (Markdown: https://insights.sbomify.com/CVE-2026-5304/index.md)
```

## Sources

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

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