SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-8983Public Intelligence Dossier
Source: autel · Limited verification•Last verified: •Collection Degraded
CVE-2026-8983Unknown / EvaluatingCRITICAL (raw)CVSS 10.0CWE-798

Autel Maxi Charger Single firmware through V1.03.51 contains a hard-coded authentication token that bypasses authorization checks for multiple management endpoints

Published: 22 Jul 2026•Last updated: 25 Oct 2026, 12:40 AM IST•Source identifier: office@cyberdanube.com
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
10.0CRITICAL (raw)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Metric sourceoffice@cyberdanube.com
EPSS probability
0.7%0.007
Percentile53rd
Weakness type
CWE-798
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Autel Maxi Charger Single firmware through V1.03.51 contains a hard-coded authentication token that bypasses authorization checks for multiple management endpoints. An attacker can supply the special token value to invoke privileged functionality without valid authentication.

SOC priority

High Severity / Review

Actively exploited (source statement)

Unknown

Publicly disclosed

Unknown

Risk basis: Microsoft or Microsoft-managed product relevance; CRITICAL severity; Critical source severity without confirmed exploitation

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • autel maxicharger single charger firmware · <= 1.03.51 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:autel:maxicharger_single_charger:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched authentication-weakness (CWE-798); network-unauthenticated (CVSS AV:N, CVSS PR:N, CVSS UI:N)

Exposure

  1. Identify affected authentication surfaces and compare versions with the advisory.Telemetry: Application inventory · A CWE match is not proof of local exposure. · Rule authentication-weakness
  2. Identify devices reporting this CVE and note which expose the affected service to untrusted networks.Telemetry: DeviceTvmSoftwareVulnerabilities · A network-reachable, no-privilege vector makes internet-facing instances the first exposure question. · Rule network-unauthenticated

Exploitation evidence

  1. Review unexpected successful sign-ins and changes to privileged accounts on affected systems.Telemetry: SigninLogs · Access anomalies are relevant to authentication weaknesses. · Rule authentication-weakness
Show more (2)

Exploitation evidence

  1. Review inbound connections to the affected service from unexpected sources since the advisory date.Telemetry: DeviceNetworkEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule network-unauthenticated

Response

  1. Verify the vendor fix and review privileged access after remediation.Telemetry: Identity audit logs · Post-change review checks the response. · Rule authentication-weakness

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
office@cyberdanube.com
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:o:autel:maxicharger_single_charger_firmware:*:*:*:*:*:*:*:american_standard, cpe:2.3:o:autel:maxicharger_single_charger_firmware:*:*:*:*:*:*:*:european_standard, cpe:2.3:h:autel:maxicharger_single_charger:-:*:*:*:*:*:*:*

Evidence & Provenance

2 public sources
nvd.nist.govSource recordcyberdanube.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-8983
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-8983
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-8983"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.