CVE-2025-1235
mediumpriority · track · 0EPSS 0.003 · 20 %ileDEEUEPSS · scored 2026-10-27
A low privileged attacker can set the date of the devices to the 19th of January 2038 an therefore exceed the 32-Bit time limit. This causes the date of the switch to be set back to January 1st, 1970.
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
The vendor does not plan to fix this; mitigate or replace.
- No fix plannedwago_psirt
Due to the low impact of the vulnerability and the fact that only the logging functionality is affected, there is no fix planned.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (26)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- VDE-2025-020WAGO: Switches affected by year 2k38 problem2025-06-02csaf · wago_psirtDE
The Year 2038 Problem affects systems using a 32-bit integer to represent time as the number of seconds since January 1st, 1970. On January 19, 2038, at 03:14:07 UTC, the time value will exceed the maximum for a 32-bit integer, causing an overflow and resetting it to a negative number.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (5)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan