The $80 million settlement resolves a major litigation overhang, but the company's stated expectation of no material financial impact (citing cyber insurance) limits the downside. The settlement is subject to court approval and a final approval hearing, which could take months. Monitor for court approval decisions and any insurance recovery disclosures in upcoming filings.
Price Chart
Executive Summary
Conduent entered into an $80 million class action settlement agreement to resolve the consolidated data breach class action lawsuit arising from its January 2025 cybersecurity incident, which exposed the private information of approximately 62 million individuals. The company states it maintains cyber insurance and does not expect the settlement to have a material impact on its financial position, results of operations, or cash flows. The settlement is subject to court approval.
Key Financial Metrics
Key Facts
- Conduent entered into a Class Action Settlement Agreement on October 16, 2026, to resolve the In re: Conduent Business Services Data Breach Litigation.
- The settlement fund is $80 million, which is Conduent's total monetary obligation and covers class member recovery, credit/medical monitoring, plaintiffs' counsel fees, and administration costs.
- The settlement resolves claims arising from a January 2025 cybersecurity incident that affected approximately 62 million individuals.
- Conduent maintains cyber insurance and does not expect the settlement to have a material impact on its financial position, results of operations, or cash flows.
- The settlement is not an admission of fault or liability and remains subject to court approval.
- The settlement releases Conduent, its affected clients, and their affected customers from claims related to the cyber incident.
- This filing follows the October 1, 2026 completion of the Transit Sale for $140 million in cash consideration, with net proceeds of $125 million intended for debt repayment.
Financial Impact
$80 million total monetary obligation, funded into a non-reversionary settlement fund. Company expects no material impact on financial position, results of operations, or cash flows due to cyber insurance.
Risk Factors
- Court may materially alter or fail to approve the settlement agreement.
- Unexpected costs or liabilities in connection with the settlement and cyber incident.
- Risk of additional litigation or regulatory actions related to the cyber incident.
- Availability and timing of cyber insurance recovery is uncertain.
Investment Themes
Documents Analyzed
This report is based on 5 SEC documents filed with EDGAR.
| Document | Accession Number |
|---|---|
| 8-K Filing (Primary) | 0001677703-26-000138 |
| Document: cndt-20261016.htm | 0001677703-26-000138 |
| Document: 0001677703-26-000138-index-headers.html | 0001677703-26-000138 |
| Document: 0001677703-26-000138-index.html | 0001677703-26-000138 |
| Document: 0001677703-26-000138.txt | 0001677703-26-000138 |
Filters
| Type | Now | ||||
|---|---|---|---|---|---|
Oct 23, 2026 3d ago | 8-K | $1.74 | awaiting T+60 | — | $1.79 (+2.87%) |
Oct 16, 2026 10d ago | 8-K | $1.38 | awaiting T+60 | — | $1.79 (+29.71%) |
Oct 15, 2026 11d ago | 8-K | $1.57 | awaiting T+60 | — | $1.79 (+14.01%) |
Oct 6, 2026 20d ago | 8-K | $1.62 | awaiting T+60 | — | $1.79 (+10.49%) |
Sep 30, 2026 26d ago | 8-K | $1.56 | awaiting T+60 | — | $1.79 (+14.74%) |
Aug 28, 2026 8w ago | 8-K | $1.72 | awaiting T+60 | — | $1.79 (+4.07%) |
Aug 10, 2026 11w ago | 8-K | $1.56 | awaiting T+60 | — | $1.79 (−14.74%) |
Aug 10, 2026 11w ago | Press Release | $1.56 | awaiting T+60 | — | $1.79 (−14.74%) |
Jul 2, 2026 16w ago | 8-K | $1.51 $1.57 | ▲ +3.97% | ▲ +0.41% | $1.79 (+18.54%) |
Jun 30, 2026 16w ago | 8-K | $1.46 $1.60 | ▲ +9.59% | ▲ +6.03% | $1.79 (+22.60%) |
US Market Status
Subscribe to SecBot
Get Real-Time SEC Filing Intelligence
Comprehensive SEC filing analysis delivered the moment filings hit EDGAR. Sentiment scoring, impact analysis, and actionable insights for every material event.
Create a free account Live analysis, Telegram alerts, watchlists and the MCP server for subscribers