A WebSocket request sent to a specific API endpoint allows unauthorized access to a separate API endpoint.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.11.106.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 12.11.106.1.
- Published
- Last modified
- 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? →
- 8/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
A WebSocket request sent to a specific API endpoint can let an attacker reach a separate API endpoint without authorization, bypassing the intended authentication layer. The attack must come from an adjacent network and requires no login or user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A WebSocket request sent to a specific API endpoint allows unauthorized access to a separate API endpoint. This bypasses the intended authentication layer.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 12.11.106.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Axis Communications AB AXIS A1210 - Secure Entry
From 11.7.12.2 · fixed in 12.11.106.1
- Axis Communications AB AXIS A1601 - Secure Entry
From 11.1.10.1 · fixed in 12.11.106.1
- Axis Communications AB AXIS A1610 - Secure Entry
From 11.4.32.2 · fixed in 12.11.106.1
- Axis Communications AB AXIS A1710
From 12.0.101.4 · fixed in 12.11.106.1
- Axis Communications AB AXIS A1810 - Secure Entry
From 12.0.101.4 · fixed in 12.11.106.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63288
Is CVE-2026-63288 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-63288?
AXIS A1210 - Secure Entry: from 11.7.12.2 before 12.11.106.1. AXIS A1601 - Secure Entry: from 11.1.10.1 before 12.11.106.1. AXIS A1610 - Secure Entry: from 11.4.32.2 before 12.11.106.1. AXIS A1710: from 12.0.101.4 before 12.11.106.1. AXIS A1810 - Secure Entry: from 12.0.101.4 before 12.11.106.1.Source: cve.now feed data
How do I fix CVE-2026-63288?
Upgrade to a fixed version: 12.11.106.1.Source: cve.now feed data