HackingFinancial ServicesFinanceSupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)LowContained

CAMBRIDGE MERCANTILE CORP. (U.S.A.)

bd_e673f27ac5ae3e2f · schema v1 · pii pii-v2

Severity

Low

Discovered

—

Filed

Sep 14, 2026

To disclose

—

Affected

Not disclosed

Linked

2 filings

Confidence

68%

Full breach record for CAMBRIDGE MERCANTILE CORP. (U.S.A.) →

Cambridge Mercantile Corp. (U.S.A.) (Corpay) notified the California AG of a data breach involving a third-party vendor, Klue. Between June 11-12, 2026, an unauthorized party accessed Corpay's CRM data via Klue's infrastructure. Affected data includes names and contact details. No credentials or financial data were compromised. Corpay engaged experts, notified law enforcement, and offered identity monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

Jun 11, 2026

Begins

Sep 14, 2026

Filed

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Massachusetts State AGbd_30c60ad8da5fb6872026-09-01 · +13dCandidate

Name: CAMBRIDGE MERCANTILE CORP. (U.S.A.)
norm: cambridge mercantile corp usa

Name: CAMBRIDGE MERCANTILE CORP. (U.S.A.)
norm: cambridge mercantile corp usa
Industry: Financial Servicesllm

Discovered: —
Breach occurred: Jun 11, 2026 – Jun 12, 2026
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain Compromise
Threat actor: External
Third party: via Klue
Initial access: supply_chain

During the incident: Engaged cybersecurity experts to investigate what had happened
Notified law enforcement
Changes made: Enhanced security and monitoring practices
Implemented additional safeguards across our own systems
Secured the services of Kroll to provide identity monitoring at no cost
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

Massachusetts State AGSep 1 · first

California State AG+13d · this page

Pattern: first filing Sep 1 (MA), last Sep 14 (CA) — a 13-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-629696
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 14, 2026
Raw hash: dbb7ed4a959ff356acdd888c2aafb44c22915348afe59996e03363a972160638

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityCAMBRIDGE MERCANTILE CORP. (U.S.A.)

Victim entityCAMBRIDGE MERCANTILE CORP. (U.S.A.)

IncidentThird-Party / Supply Chain

Stated responseEngaged cybersecurity experts to investigate what had happened

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov