Authentication bypass with privileged access in Danfoss AK-SM 8xxA Series prior to version 4.2
Not confirmed exploited. No WAF vendor names it yet. 1 public exploit repo.
Improper Authentication vulnerability in Danfoss AKSM8xxA Series.This issue affects Danfoss AK-SM 8xxA Series prior to version 4.2
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable over the network under specific conditions, with no privileges and user interaction, leading to full loss of confidentiality and availability and low impact on integrity, and the impact can reach components beyond the vulnerable one.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityThe attack only works when conditions outside the attacker's control line up.High
- Privileges requiredNo account or login is needed.None
- User interactionA user has to do something first, such as open a file or click a link.Required
- ScopeThe attack can spread beyond the vulnerable component to other parts of the system.Changed
- Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impactAn attacker can change some data, but with limited control or limited effect.Low
- Availability impactAn attacker can take the component down completely or keep it from serving anyone.High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:HPublic exploit code or a detailed write-up exists, but CISA has not seen attacks.
At least one step needs hands-on work, which slows mass attacks.
A successful attack gives limited control over the affected software or limited access to its data.
Public exploits
1 foundNo exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-05-08CVE publishedCVE List
- 2026-11-02First public exploit repositoryGabrieleDattile/CVE-2025-41450-Fromagegate: Technical post-mortem, vulnerability analysis, and OT defense blueprint for CVE-2025-41450 & the October 2026 Fromagegate retail cold-chain sabotage incident.
- 2026-11-02
Vendor statements
QuotedCloudflareWAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each signature lists the CVEs it references, with its id and date. F5 does not state a default action; signatures enforce once staging ends in your policy.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
Exploit repos · unvetted, don't run
GabrieleDattile/CVE-2025-41450-Fromagegate: Technical post-mortem, vulnerability analysis, and OT defense blueprint for CVE-2025-41450 & the October 2026 Fromagegate retail cold-chain sabotage incident.
Top posts
@visegrad24 The attacks exploit Danfoss units AK-SM 800, AK-SM 800A, and AK-SC 355 controllers (CVE-2025-41450 and CVE-2025-41451) but patched units are NOT susceptible; the compromises occur when commercial facilities leave outdated firmware or obsolete, end-of-life models expo…
@zerohero7646 @TrungTPhan No confirmed backdoors. Attacks exploited known firmware flaws in Danfoss (and similar) controllers, mainly a predictable "code-of-the-day" authentication bypass generated from the device date (CVE-2025-41450). Devices were left exposed on the public in…
@porobertdev @real_Miroslav @themegatriumph @InsiderGeo The Danfoss AK-SM 800A "code of the day" auth bypass (CVE-2025-41450) was disclosed and patched by March–May 2025, with CISA advisory that year. Claroty publicly detailed it in August 2026. Copeland XWEB had related flaws n…