Live  /  Secomea  /  Incident

Secomea: CVE-2026-98432: Investigation ongoing

Secomea · secomea.comMajor incidentResolved2026-11-04 12:32 UTC
Public — what happened

Summary

Secomea said it began checking on October 30, 2026 at 10:31 UTC whether a security vulnerability labeled CVE-2026-98432 affects its products and services. The company described this as a precaution, said it was not under attack, and noted it had temporarily closed access to Secomea Prime, while customers could still sign in directly through their GateManager address. Updates on October 30 and November 2 said the investigation was continuing, with no findings or required customer actions shown in the text provided. The incident is marked resolved as of November 4, 2026 at 12:32.

Affected

Knowledgebase, GateManager 00, Prime Platform, GateManager 01, License Portal, FTP, GateManager 02, Mail Relay 1, GateManager 03, Mail Relay 2, GateManager 04, NTP, GateManager 06, GateManager 08, GateManager 10, GateManager 11, GateManager 12, GateManager 14, GateManager 16, GateManager 21, GateManager 22, GateManager 23, GateManager 41, GateManager 51 and 16 more

As listed on Secomea’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Secomea against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Secomea: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Secomea report →

More from Secomea

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Secomea status & history page.

Related: Secomea status & history. SquidGrid is not affiliated with Secomea.