# CVE-2025-9524: Denial of service in AXIS OS

> Authenticated attackers can crash the VAPIX API process, causing denial of service on Axis network cameras.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-3ghv-qqmp-p6c4

## What is CVE-2025-9524?

CVE-2025-9524 is a medium-severity denial of service vulnerability in AXIS OS, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The VAPIX API port.cgi did not have sufficient input validation, which may result in process crashes and impact usability. This vulnerability can only be exploited after authenticating with a viewer- operator- or administrator-privileged service account.

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

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


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

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

## Is CVE-2025-9524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9524 is a medium-severity denial of service vulnerability in AXIS OS, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9524 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-2025-9524/ (Markdown: https://insights.sbomify.com/CVE-2025-9524/index.md)
```

## Sources

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

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