VulnerabilityPublished 10 Nov 2026

CVE-2026-14543: AXIS OS · Improper Validation of Specified Type of Input

Affects AXIS OSSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.9 Low : upgrade to 13.0.42 or 12.11.84 when convenient.

Data as of 10 Nov 2026, 05:39 UTC

CVSS 3.1 base score

3.9Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Axis)	CVSS 3.1	3.9

Patch: Available – fixed in 13.0.42, 12.11.84

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade AXIS OS and axis/axis-os to 13.0.42 or 12.11.84.

Affected software

Product	Affected	Fixed in
Axis Communications ABAXIS OS	Affected >=13.0.0 <13.0.42	Fixed in 13.0.42
Axis Communications ABAXIS OS	Affected >=12.0.0 <12.11.84	Fixed in 12.11.84
Axisaxis/axis-os`pkg:rpm/axis/axis-os`Other threats	Affected >=12.0.0 <12.11.84 >=13.0.0 <13.0.42	Fixed in 12.11.84 13.0.42

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in AXIS OS versions 12.11.84 and 13.0.42. Users should upgrade affected systems to these or later versions to remediate the vulnerability. Since exploitation requires authentication with an admin-privileged account, ensuring strong credential management and limiting admin access can reduce risk. No additional vendor advisories indicate other mitigations or that no action is required.

Description

CVE-2026-14543 is a vulnerability in Axis Communications AB AXIS OS affecting the VAPIX Edge storage API. It allows privilege escalation by bypassing filesystem isolation, granting unauthorized access to protected system resources. Exploitation requires authentication with an admin-privileged service account. The flaw affects AXIS OS versions 12.0.0 up to but not including 12.11.84 and 13.0.0 up to but not including 13.0.42. A fix is available in versions 12.11.84 and 13.0.42. The CVSS score is 3.9, indicating low severity with high confidentiality impact but no impact on integrity or availability.

Impact

Successful exploitation allows an attacker with admin-level authenticated access to escalate privileges by bypassing filesystem isolation, resulting in unauthorized access to protected system resources. The confidentiality of the system is compromised, but integrity and availability are not affected. The attack complexity is low but requires physical access and high privileges, limiting the exploitability.

Summary

This vulnerability (CVE-2026-14543) in AXIS OS involves improper validation of input types in the VAPIX Edge storage API, which enables an authenticated attacker with admin privileges to escalate user privileges by circumventing filesystem isolation. This leads to unauthorized access to protected system resources. The vulnerability affects AXIS OS versions >=12.0.0 <12.11.84 and >=13.0.0 <13.0.42. The issue is fixed in versions 12.11.84 and 13.0.42. The CVSS 3.1 vector indicates the attack requires physical access (AV:P), low attack complexity (AC:L), high privileges (PR:H), no user interaction (UI:N), unchanged scope (S:U), high confidentiality impact (C:H), and no impact on integrity or availability (I:N, A:N). No known exploits are reported in the wild.

CWE-1287Improper Validation of Specified Type of Input (opens in a new tab)
Base weakness
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

axis.com/dam/public/cd/92/6b/cve-2026-14543pdf-en-US-561257.pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 05:39 UTC

WeaknessesCWE-1287, CWE-732

Technical details

References

Community reviews

Related threats