CVE-2025-58587 json
Improper Restriction of Excessive Authentication Attempts
published 2025-10-06 13 mo ago modified 2026-10-18 21 d ago also EUVD-2025-32199
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
The application does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it possible for an attacker to guess user credentials.
Patch / fix
- SICK AG Baggage Analytics 4.6.3
- SICK AG Tire Analytics 4.6.3
- SICK AG Package Analytics 4.6.3
- SICK AG Logistic Diagnostic Analytics 4.6.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- SICK AG Baggage Analytics
- SICK AG Tire Analytics
- SICK AG Package Analytics
- SICK AG Logistic Diagnostic Analytics
- SICK AG Enterprise Analytics
Classification
- Weakness
-
- CWE-307 Improper Restriction of Excessive Authentication Attempts
References
-
sick.com
/.well-known/csaf/white/2025/sca-2025-0010.pdf
vendor-advisory
-
sick.com
/psirt
vendor-advisory
-
sick.com
/.well-known/csaf/white/2025/sca-2025-0010.json
vendor-advisory
-
sick.com
/media/docs/9/19/719/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
product
-
cisa.gov
/resources-tools/resources/ics-recommended-practices
us-government-resource
-
first.org
/cvss/calculator/3.1
not-applicable
Sources
- CVE List CVE-2025-58587
- NVD CVE-2025-58587
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.