VulnerabilityPublished 10 Nov 2026

CVE-2026-13409: VAPIX API dynamicoverlay.cgi which results

Source GCVE Database

Compare

Authoritative record:CVE-2026-13409· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium · fixed in 13.0.31 : update AXIS OS when convenient.

Data as of 10 Nov 2026, 07:17 UTC

CVSS 3.1 base score

4.3Medium

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	4.3

Patch: Available – fixed in 13.0.31, 12.11.84, 11.11.218 +2

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.

ghsa-qf9x-fppw-p385

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Axis Communications ABAXIS OS	Affected >=13.0.0 <13.0.31	Fixed in 13.0.31
Axis Communications ABAXIS OS	Affected >=12.0.0 <12.11.84	Fixed in 12.11.84
Axis Communications ABAXIS OS	Affected >=11.0.0 <11.11.218	Fixed in 11.11.218
Axis Communications ABAXIS OS	Affected >=10.0.0 <10.12.345	Fixed in 10.12.345
Axis Communications ABAXIS OS	Affected >=9.0.0 <9.80.148	Fixed in 9.80.148

AI-suggested

Since the vulnerability requires authenticated operator or admin privileges, restricting access to these accounts and monitoring their use may reduce risk.

Description

CVE-2026-13409 is a vulnerability in the VAPIX API's dynamicoverlay.cgi endpoint that causes a denial-of-service (DoS) affecting the overlay functionality. Exploitation requires authentication with an operator or admin-privileged service account. The vulnerability does not impact confidentiality or integrity but results in availability loss of the overlay feature.

Impact

Successful exploitation results in denial-of-service of the overlay functionality, impacting availability. There is no impact on confidentiality or integrity. The attack requires authenticated access with elevated privileges, limiting the attack surface to authorized users.

Summary

The vulnerability identified as CVE-2026-13409 affects the VAPIX API's dynamicoverlay.cgi component. It allows an authenticated user with operator or admin privileges to cause a denial-of-service condition that disrupts the overlay functionality. The CVSS v3.1 score is 4.3 (medium severity), reflecting network attack vector, low attack complexity, required privileges, no user interaction, and impact limited to availability. No public exploits or known in-the-wild exploitation have been reported.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
The product writes past the end of a buffer that was allocated on the stack.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 07:17 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats