dbcve.org
Axis OsOperating system · Axis

CVE-2025-11142

HIGH · 8.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 12.7.36 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The VAPIX API mediaclip.cgi that did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator- privileged service account.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The VAPIX API mediaclip.cgi endpoint lacks sufficient input validation, allowing authenticated operators or administrators to potentially execute arbitrary code on Axis devices. This is a classic RCE vulnerability stemming from improper sanitization of user-supplied input.

MitigationApply vendor-provided patches when released; in the interim, strictly limit VAPIX API access to trusted personnel only, enforce least-privilege principles for service accounts, and monitor for anomalous authenticated requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Axis OsOperating system
Affected:>= 12.6.54, < 12.7.36

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is an Axis device running Axis OS
    Access the device web interface or query the device via VAPIX API (e.g., GET /vapix/sysinfo or check the login page for Axis branding). Identify the Axis OS version from system information pages or VAPIX response.
    Affected if Device is not an Axis device or does not run Axis OS
  2. Determine the installed Axis OS version
    Log into the device web interface and navigate to System > About, or query the VAPIX API endpoint (e.g., /vapix/cgi-bin/sysinfo.cgi or similar). Locate the firmware/OS version string.
    Affected if Version is >= 12.6.54 and < 12.7.36 (within the affected range)
  3. Verify VAPIX API is accessible
    Attempt to reach the device at the /vapix/ path via HTTP or HTTPS (e.g., curl http://<device-ip>/vapix/). Check if the API responds or prompts for authentication.
    Affected if VAPIX API endpoint responds and is accessible from the network
  4. Confirm mediaclip.cgi endpoint is reachable
    Send an authenticated request to the mediaclip.cgi endpoint (e.g., GET /vapix/mediaclip.cgi). Use valid VAPIX operator or administrator credentials.
    Affected if mediaclip.cgi responds (even with an error) indicating the endpoint exists and is accessible with valid credentials

Device is affected if it is an Axis device running Axis OS version 12.6.54 or higher but below 12.7.36, the VAPIX API is network-accessible, and the mediaclip.cgi endpoint can be accessed with valid operator/administrator credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.7.36 or later
Fixed in 12.7.36
Interim mitigation

Apply vendor-provided patches when released; in the interim, strictly limit VAPIX API access to trusted personnel only, enforce least-privilege principles for service accounts, and monitor for anomalous authenticated requests.

Recommended fix High confidence

Axis OS version 12.7.36 or later

  1. 1. Access the Axis device web interface or use the Axis Device Manager tool
  2. 2. Navigate to the System or Settings section
  3. 3. Locate the firmware upgrade option
  4. 4. Download the latest Axis OS firmware version 12.7.36 or later from the official Axis website (www.axis.com)
  5. 5. Upload and apply the firmware update to the device
  6. 6. Verify the device reboots successfully and the new firmware version is installed
  7. 7. Confirm the VAPIX API mediaclip.cgi endpoint is now patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axis Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11142 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data