CVE-2026-22102: Arbitrary file overwrite through certificate update functionality
A POST request sent to a specific webserver endpoint can be used to write to arbitrary file locations. The endpoint accepts the filename parameter in the Content-Disposition header without verification.
This can be used to cause a denial of service by overwriting system files, or remote-code-execution by overwriting shell-scripts which execution can be triggered through other means.
Security readout for executives and security teams
Plain-English summary
CVE-2026-22102 is a critical flaw in EVbee DC-80 certificate update handling. An unauthenticated network request can make the device write attacker-chosen file names, potentially damaging system files or enabling remote code execution if another process later runs an overwritten script.
Executive priority
Treat this as urgent for any exposed EVbee DC-80 deployment. The flaw is unauthenticated, network-accessible, and can affect both service availability and device integrity. Prioritize asset discovery, exposure reduction, and vendor guidance review.
Technical view
The vulnerable webserver endpoint trusts the filename value from the Content-Disposition header during certificate update processing. Missing input validation enables arbitrary file overwrite. The CVSS 4.0 score is 9.3 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to EVbee DC-80 version 0 as listed in the CVE source bundle. Internet-facing or broadly reachable management interfaces would materially increase risk. The bundle does not establish impact for other EVbee products or versions.
Exploitation context
The bundle states arbitrary overwrite can cause denial of service or remote code execution when overwritten scripts are triggered separately. CISA KEV status is false in the provided data, and no cited source in the bundle confirms active exploitation.
Researcher notes
Evidence is strong for the vulnerability class and severity, but incomplete on patch availability, exact endpoint naming, and observed exploitation. Avoid assuming broader product impact. Focus validation on affected DC-80 instances, reachable management surfaces, and signs of unauthorized file overwrite.
Mitigation direction
Identify EVbee DC-80 assets and confirm affected version information.
Check EVbee and DIVD guidance for firmware updates or official mitigations.
Remove public access to the webserver management interface where feasible.
Restrict administration access to trusted networks or VPN paths.
Monitor for unexpected certificate update requests and file integrity changes.
Validation and detection
Inventory EVbee DC-80 devices and record firmware or product version evidence.
Confirm whether the certificate update web endpoint is reachable from untrusted networks.
Review webserver logs for unusual POST requests to certificate update functionality.
Check critical system files and scripts for unexpected modification times.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.