dbcve.org
Axis OsOperating system · Axis

CVE-2026-1185

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 12.10.37 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
A configuration file on the local file system had improper input validation which could allow code execution and potentially lead to privilege escalation. This vulnerability can only be exploited if an attacker can log in to the Axis device using SSH.

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

Improper input validation in a local configuration file on Axis devices allows an attacker with SSH login credentials to inject malicious input, potentially achieving arbitrary code execution and privilege escalation from authenticated user level.

MitigationRestrict or disable SSH access to Axis devices to trusted personnel only, and apply vendor-supplied security patches when available.

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.0.0, < 12.10.37

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. Identify the installed Axis OS version
    Log into the Axis device web interface and navigate to System > About, or use SSH to run 'show version' or 'cat /etc/os-release' to retrieve the firmware version number
    Affected if The version falls within 12.0.0 to 12.10.36 (inclusive)
  2. Confirm SSH access is enabled
    Via web interface: System > Network > SSH, or via SSH run 'sshd status' or check /etc/ssh/sshd_config to verify the SSH daemon is actively running
    Affected if SSH service is enabled and accessible on the device
  3. Check for existing SSH users with elevated privileges
    Via web interface: Settings > Users, or via SSH run 'cat /passwd' to list user accounts and their privilege levels
    Affected if Any authenticated SSH user exists on the device (the vulnerability allows privilege escalation from any authenticated user level)
  4. Inspect the vulnerable local configuration file
    Locate and examine the local configuration file referenced in the device's service documentation or configuration paths (e.g., under /etc or /config) for any user-controllable parameters that lack input validation
    Affected if The configuration file accepts user-supplied input without proper sanitization

Your device is affected if it runs Axis OS version 12.0.0 through 12.10.36, has SSH access enabled, and contains any authenticated user accounts that could inject malicious input into the vulnerable configuration file.

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.10.37 or later
Fixed in 12.10.37
Interim mitigation

Restrict or disable SSH access to Axis devices to trusted personnel only, and apply vendor-supplied security patches when available.

Recommended fix High confidence

Axis OS version 12.10.37 or later

  1. 1. Access the Axis device management interface or use the Axis IP utility to identify the device on the network
  2. 2. Navigate to the device's web interface and log in with administrator credentials
  3. 3. Go to System > Maintenance or Settings > System > Maintenance (depending on UI version)
  4. 4. Locate the firmware/OS version information to confirm current version is between 12.0.0 and 12.10.36
  5. 5. Download the latest Axis OS version 12.10.37 or later from the official Axis website (www.axis.com) under support/drivers-software
  6. 6. In the maintenance section, select 'Upgrade' and upload the downloaded .axf file
  7. 7. Wait for the upgrade process to complete - do not power off the device during this time
  8. 8. After reboot, verify the new OS version is 12.10.37 or higher via System > About or Settings > System > About
Caveat Review Axis release notes for any configuration or feature changes between your current version and 12.10.37 before upgrading

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1185 — 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-2026-1185 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