One linked filing — more sources may join as they report · filed May 8, 2026. View entity profile → Other incidents for this victim →
incident inc_133d8860fbc941ba · merge_method deterministic
Discovered → first regulatory filing
Discovery to SEC materiality determination
IP / system
Materiality determination to SEC 8-K filing
Not recorded for this incident
Discovery variance · Leak precedence · Filing span — no leak-site claim in this cluster; needs two dated filings.
FEDERAL
all SEC 8-K
Earliest sighting first · deep chronology in Litigation Timeline
Apr 20, 2026
Reported by SEC 8-K filing
May 8, 2026
Registrant determined the incident material — starts the SEC 4-business-day clock
SailPoint, Inc. disclosed on May 8, 2026, that on April 20, 2026, unauthorized access was detected in a subset of its GitHub repositories. The access was caused by a vulnerability in a third-party application, which has been remediated. The company states that no customer data in production or staging environments was accessed, services were not interrupted, and affected customers were directly notified.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.