The Signed Video Framework contained a out-of-bounds read issue in the Signed Video Framework which could lead the application using this…
- Exploited
- No known exploitation
- Fix
- Fixed in Signed Video Framework 2.3.7 · Signed media verifier 1.0.3 · Axis File Player 3.1.10.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: Signed Video Framework 2.3.7 · Signed media verifier 1.0.3 · Axis File Player 3.1.10.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.17% · 6th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Signed Video Framework has an out-of-bounds read flaw that can crash applications using it, and it affects only the tools that validate signed content, not the signed video functionality on AXIS OS devices. An attacker can reach it remotely and without logging in, but a user must first take an action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Signed Video Framework contained a out-of-bounds read issue in the Signed Video Framework which could lead the application using this framework to crash. The issue exclusively affects the tools used for the validation of signed content. The AXIS OS device's signed video functionality remains unaffected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: Signed Video Framework 2.3.7 · Signed media verifier 1.0.3 · Axis File Player 3.1.10.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-14918 (The Signed Video Framework contained a out-of-bounds read issue in the Signed Video Framework which could lead the application using this…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-14918 (entry last updated 2026-11-10): Affected: - Axis Communications AB Signed Video Framework: fixed in 2.3.7 - Axis Communications AB Signed media verifier: fixed in 1.0.3 - Axis Communications AB Axis File Player: fixed in 3.1.10.0 Fixed versions: 2.3.7, 1.0.3, 3.1.10.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-14918 is not listed as of cve.now's last read. This KEV status is for CVE-2026-14918 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.axis.com/dam/public/3b/4f/06/cve-2026-14918pdf-en-US-561258.pdf Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-14918 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-14918.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Axis Communications AB Signed Video Framework
fixed in 2.3.7
- Axis Communications AB Signed media verifier
fixed in 1.0.3
- Axis Communications AB Axis File Player
fixed in 3.1.10.0
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-14918
Is CVE-2026-14918 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-14918?
Signed Video Framework: before 2.3.7. Signed media verifier: before 1.0.3. Axis File Player: before 3.1.10.0.Source: cve.now feed data
How do I fix CVE-2026-14918?
Upgrade to a fixed version: Signed Video Framework 2.3.7 · Signed media verifier 1.0.3 · Axis File Player 3.1.10.0.Source: cve.now feed data