Skip to content
major vulnerability· requires attention

Unauthenticated path traversal in widely deployed BACnet building-automation devices enables file overwrite and full device compromise, risking facility operations across many sectors.

OT/ICS

CVE-2025-41753

9.3
Critical
EPSS n/aPatch availableOct 1, 2026

Unauthenticated BACnet path traversal allows arbitrary file read/overwrite.

common questions

Is CVE-2025-41753 being exploited?

Not confirmed. CVE-2025-41753 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2025-41753?

CVE-2025-41753 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-41753?

Yes. A fix has been recorded for CVE-2025-41753. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-41753 affect?

CVE-2025-41753 affects BACnet-enabled building automation systems, BMS/BAS controllers (HVAC, access control), BACnet gateways and IoT controllers, Building management sensors and controllers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-41753?

Isolate BACnet devices, restrict BACnet network access, apply vendor patches when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
BACnet-enabled building automation systemsBMS/BAS controllers (HVAC, access control)BACnet gateways and IoT controllersBuilding management sensors and controllers
impact

Unauthenticated remote path traversal in BACnet File Object lets attackers read/overwrite arbitrary files, enabling device takeover and lateral movement.

action required

Immediate action required

affected versions
WAGO 0750-811x-xxxx-xxxx
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0750-821x-xxx-xxx
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0751-9x01
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0752-8303-8000-0002
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-340x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-420x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-430x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-520x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-530x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-620x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)
WAGO 0762-630x-8000-000x
  • affected>= 1.0.0 and < 4.8.9
  • affected>= 1.0.0 and < 4.8.9 (70)

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free