CVERadar
HIGH · CVSS 3.1 8.2Public PoCEPSS 0.95% (p61)Threat level 45

CVE-2025-41450: CVE-2025-41450: Improper Authentication vulnerability in Danfoss AKSM8xxA Series.This issue affects Danfos…

Unknown · · NVD published 2025-05-08 · posted 2026-10-13 · last modified 2026-10-20

CVE-2025-41450 at a glance

CVE-2025-41450 is a high-severity vulnerability in the affected product, with a CVSS 3.1 base score of 8.2. NVD published it on 2025-05-08 and classifies the weakness as CWE-305. Public exploit code: 3 public GitHub proof-of-concept repositories from 3 accounts, with the earliest exploit evidence dated 2026-10-13. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.95% (percentile 61.2, scored 2026-11-03). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 45/100.

What it is

Improper Authentication vulnerability in Danfoss AKSM8xxA Series.This issue affects Danfoss AK-SM 8xxA Series prior to version 4.2

WeaknessCWE-305 definition
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:H (source: CVE Numbering Authority)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-10-13 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2026-10-13. Most starred: msuiche/fromagegate (9 stars), view the msuiche/fromagegate repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources