The Cleverbridge data breach has exposed payment card numbers, expiry dates and CVV or CVC security codes. The e-commerce and subscription billing provider detected unauthorised activity on 4 November 2026 and began notifying affected individuals on 20 November.
The incident affects payment card data stored on Cleverbridge’s platform. However, the company has not disclosed how attackers gained access, how many records were copied or which merchants and transactions were affected.
What happened in the Cleverbridge data breach?
Cleverbridge provides checkout, e-commerce and recurring billing services for software and software as a service vendors. On 4 November 2026, the company identified unauthorised activity affecting its platform and temporarily took affected systems offline while it worked to contain the incident.
Cleverbridge’s public status history records a platform availability incident between 09:53 and 19:06 UTC that day. The systems were restored on 4 November, and the company’s status page showed all services operating normally as of 22 November 2026.
An investigation subsequently found that an unauthorised third party had copied payment card information stored on the platform. Customer notification letters identify the compromised fields as:
- Payment card numbers
- Card expiry dates
- CVV or CVC security codes
The notices state that other personal information, including names, contact information and billing details, was not copied. This limits the types of personal data involved, but the combination of a card number, expiry date and security code can still be sufficient for attempted card-not-present payments.
Cleverbridge said the incident was not a ransomware attack and that its systems were not encrypted. It notified data protection authorities, law enforcement agencies, payment card networks and payment partners about the Cleverbridge data breach.
Cleverbridge data breach timeline
Unauthorised activity detected on 4 November
Cleverbridge detected the suspicious platform activity on 4 November 2026. It temporarily took affected systems offline to contain the activity and restored service later that day.
The recorded availability incident, from 09:53 to 19:06 UTC, provides an independently documented window for the operational disruption. Cleverbridge has not said whether the attacker accessed the platform only during this period or had been present before detection.
Customer notifications began on 20 November
The company began sending notifications to affected individuals on 20 November 2026. Reports from users on vendor community forums confirm that customers have received emails stating that their card details were copied on 4 November.
The Cleverbridge data breach became publicly reported on 22 November 2026. As of that date, the company had not disclosed the total number of affected cardholders, the number of merchants involved or the geographical distribution of those affected.
How the payment card theft occurred
Cleverbridge has said that a third party copied card data stored on its e-commerce platform, but it has not published further technical details. There is no confirmed information about the initial access method, the attacker’s dwell time, the systems accessed or whether stolen data was encrypted at rest.
The company has also not identified the threat actor. No malicious IP addresses, domains, file hashes, system paths or other indicators of compromise had been published as of 22 November 2026.
This means the Cleverbridge data breach is a confirmed data exfiltration incident, not a newly disclosed software vulnerability. There is no proof of concept or security update for customers to apply, and no affected software version has been identified.
Why the inclusion of CVV or CVC matters
A CVV or CVC is the short security code used to help verify that a buyer possesses a payment card. Its inclusion alongside the card number and expiry date increases the risk that criminals could attempt online or telephone transactions where the physical card is not required.
Payment Card Industry Data Security Standard requirements prohibit storing card verification codes after payment authorisation. The information in the customer notices may therefore raise compliance questions, although it does not, by itself, establish how Cleverbridge handled the data or at what stage it was copied.
Which customers and transactions are affected?
The known scope covers transactions processed through Cleverbridge where payment card data was stored on its platform. Cleverbridge has not identified particular checkout products, integration types, merchant programmes or software versions as affected.
It has also not provided an exact transaction period beyond identifying 4 November 2026 as the date when the unauthorised activity was detected and the card information was copied. Customers should rely on a direct notification from Cleverbridge or advice from their card issuer when determining whether a particular card was exposed.
Cleverbridge publicly lists a range of technology companies as customers, including Red Hat, SUSE, Tenable, Veeam, Jamf, Sony and Parallels. Their appearance on that list does not confirm that their customers were involved in the Cleverbridge data breach. The company has not named any affected merchant.
Current exploitation and fraud risk
The theft itself is confirmed, but there was no public evidence as of 22 November 2026 that the stolen data set had been advertised, sold or released online. There were also no publicly confirmed fraudulent transactions linked to the incident.
Nevertheless, complete card details create an immediate potential for card-not-present fraud. Criminals may attempt small test payments before larger purchases, so even low-value unfamiliar transactions could be relevant.
Credit monitoring can help identify certain forms of identity misuse, but it does not prevent unauthorised card payments. Prompt contact with the card issuer is the most direct way to assess whether a card should be blocked or replaced.
Why the Cleverbridge data breach matters to UK firms
UK organisations may use company cards to buy software or subscriptions from vendors that process payments through Cleverbridge. A business does not need to have a direct contractual relationship with Cleverbridge for its payment card to have passed through the platform.
The lack of a published merchant list means finance and procurement teams cannot determine exposure from supplier names alone. They should check relevant purchasing mailboxes and staff accounts for a Cleverbridge notification, while avoiding assumptions that every Cleverbridge transaction was affected.
Actions for potentially affected organisations
Businesses that receive a notification should act on the specific card identified and follow their issuer’s instructions. Appropriate steps include:
- Reviewing statements for unfamiliar transactions, particularly activity from early November onwards.
- Contacting the card issuer to report the exposure and ask whether replacement is recommended.
- Checking shared finance, procurement and employee mailboxes for Cleverbridge notices.
- Alerting finance staff so that suspicious payment attempts are escalated promptly.
- Using fraud assistance or monitoring services offered through TransUnion’s Cyberscout where eligible.
Cleverbridge says it is providing affected customers with notification, credit monitoring and fraud assistance through Cyberscout. Organisations should use contact details obtained independently from their bank or the official Cleverbridge website rather than relying on links in unexpected messages, as breach notifications can also attract impersonation attempts.
Originally reported by BleepingComputer.







