CVE-2025-59787: 2N Telekomunikace a.s 2N Access Commander · – Improper Check or Handling of Exceptional Conditions
Affects 2N Telekomunikace a.s 2N Access CommanderSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.5 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade 2N Telekomunikace a.s 2N Access Commander to 3.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| 2N Telekomunikace a.s.2N Access Commander | Affected
| Fixed in
|
AI-suggested
Organizations should prioritize updating 2N Access Commander to the latest version once a patch addressing CVE-2025-59787 is released by 2N Telekomunikace a.s. In the absence of an official patch, implement network-level protections such as Web Application Firewalls (WAFs) configured to detect and block malformed or suspicious HTTP requests targeting the Access Commander application. Employ strict input validation and sanitization rules at the perimeter to prevent malformed requests from reaching the application. Limit network exposure of the Access Commander interface by restricting access to trusted internal networks or VPNs, reducing the attack surface. Monitor application logs and network traffic for unusual HTTP 500 error spikes that may indicate exploitation attempts. Conduct regular security assessments and penetration testing focused on input validation and error handling to identify and remediate similar issues proactively. Engage with the vendor for timely updates and security advisories. Additionally, implement redundancy and failover mechanisms for access control systems to maintain availability in case of service disruption.
Description
2N Access Commander application version 3.4.2 and prior returns HTTP 500 Internal Server Error responses when receiving malformed or manipulated requests, indicating improper handling of invalid input and potential security or availability impacts.