CVSS 3.1
8.3 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LCVE-2026-63288 axis communications ab
High (8.3) in axis communications ab. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
A WebSocket request sent to a specific API endpoint allows unauthorized access to a separate API endpoint. This bypasses the intended authentication layer.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-306 Missing Authentication for Critical Functionality
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- Assigned by
- Axis (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-63288 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63288?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63288?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63288 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-63288)
HTML:
<a href="https://cve.bz/cve/CVE-2026-63288"><img src="https://cve.bz/cve/badge/CVE-2026-63288.svg" alt="CVE-2026-63288"></a>
Affected
- axis communications ab:axis a1210 - secure entry
- axis communications ab:axis a1601 - secure entry
- axis communications ab:axis a1610 - secure entry
- axis communications ab:axis a1710
- axis communications ab:axis a1810 - secure entry
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Axis Communications AB AXIS A1210 - Secure Entry | from 11.7.12.2 before 12.11.106.1 |
| Axis Communications AB AXIS A1601 - Secure Entry | from 11.1.10.1 before 12.11.106.1 |
| Axis Communications AB AXIS A1610 - Secure Entry | from 11.4.32.2 before 12.11.106.1 |
| Axis Communications AB AXIS A1710 | from 12.0.101.4 before 12.11.106.1 |
| Axis Communications AB AXIS A1810 - Secure Entry | from 12.0.101.4 before 12.11.106.1 |
Attack patterns (CAPEC)
- CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
- CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-166 Force the System to Reset Values Severity: Medium
- CAPEC-216 Communication Channel Manipulation
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.