Live / IDnow / Incident
IDnow: Security Information - no impact on IDnow services - PHP2Shell (CVE-2026-109618, CVE-2026-109619)
IDnow · idnow.deMinor incidentResolved2026-11-03 10:18 UTC
Public — what happened
Summary
IDnow posted a security notice about two serious flaws in the PHP programming software, known as PHP2Shell, which the PHP project addressed with emergency updates on 21 October 2026. IDnow said it checked its systems once the fixes were published and that none of its products or services use a vulnerable version. It also said its public website was reviewed and is fully updated, and that customers need not take any action. The notice began on 23 October 2026, offered a call with its security team for anyone wanting details, and was marked resolved on 3 November 2026.
Affected
Ident Center Munich, VideoIdent, VideoIdent, Ident Center Iasi, eID, eID, AutoIdent, Ident Center Split, AutoIdent, AutoIdent QES, AutoIdent QES, Ident Center Athens, Ident Center Zagreb, POS, POS, Check'nSign.io, Check'nSign.io, Ident Center Osijek, IDCheck.io, IDCheck.io, Ident Center Metkovici, Ident Center Brasov, ETSI, ETSI and 16 more
Timeline
- Started — 2026-10-23 13:17 UTC
- Monitoring — 2026-10-23 13:17 UTC
- Resolved — 2026-11-03 10:18 UTC · 11 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach IDnow against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for IDnow: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the IDnow report →
More from IDnow
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.