Skip to content
All posts

CVE-2024-49138 Hit 782 POS Terminals, 1M Cards: What to Do

November 20, 2026 · Team PlayCISO
TL;DR · the short version

Cybernews researchers say they found an attacker's server left open on the internet in August 2026 holding malware source code, exploitation tools and a carding panel, "VINY JUNIOR TRILHAS", with more than one million payment card records taken from 782 compromised Windows point-of-sale systems: 677 in Brazil, 22 in the United States and 8 in Russia, across 20 countries. The attacker used CVE-2024-49138, a Windows Common Log File System driver elevation-of-privilege flaw that Microsoft fixed on 10 December 2024 and CISA listed as exploited the same day, to gain SYSTEM rights, then installed a remote access trojan that captured card data during transactions. The records held card numbers, expiry dates, BINs, issuing bank and country, and card type and brand. How the attacker first got onto the systems is not stated, and whether the million records are de-duplicated is not clear. The server was offline from 31 August; Cybernews told Brazil's CERT on 8 September. For retailers the lesson is old and expensive: patch Windows on POS, retire unsupported builds, allow-list and segment the POS estate, and remove clear card data from it with point-to-point encryption or tokenisation.

Put it into practice
Rank the exploited flaws on your estate first
Put KEV-listed, exploited bugs like CVE-2024-49138 ahead of the long tail, starting with systems that touch card data.
Open the vulnerability prioritizer

An attacker used a Windows flaw patched in December 2024 to steal card data from 782 point-of-sale (POS) systems, according to Cybernews researchers. Cybernews says it found the attacker's server left open on the internet in August 2026, holding malware source code, exploitation tools and a carding panel with more than one million payment card records. Most of the systems were in Brazil (677); 22 were in the United States. The flaw, CVE-2024-49138, gave the attacker SYSTEM rights on machines it had already reached; how it reached them is not stated. Neither the merchants nor the banks involved have been named, and none has confirmed the figures.

Who this is for: CISOs and security leads at retailers, hospitality and payment service providers, and anyone who owns PCI DSS compliance or a Windows-based POS estate.

Cybernews's own page refused our requests on 20 November 2026, so the research details below come from coverage that cites it (TechRadar, IT Finanzmagazin, Secure Blink) and agrees on the facts. Every figure is Cybernews's. We checked the CVE at CISA, NVD and Microsoft's record. PlayCISO is not affiliated with Cybernews or Microsoft. We publish no indicators, card data or exploit details.

Confirmed vs not yet known

  • Confirmed (primary sources): CVE-2024-49138 is a Windows Common Log File System (CLFS) driver elevation-of-privilege flaw (CVSS 7.8, local). Microsoft fixed it on 10 December 2024; CISA added it to the Known Exploited Vulnerabilities catalog the same day, with a 31 December 2024 deadline for US federal agencies.
  • Reported by Cybernews (not independently verified): an exposed attacker server; 782 compromised POS systems in 20 countries; more than one million card records; the carding panel "VINY JUNIOR TRILHAS"; a remote access trojan that captured card data during transactions; the attacker adapted public proof-of-concept code for the CVE.
  • Assessed, not confirmed: Cybernews thinks the operator is Brazilian, from the language of documents on the server.
  • Not known: how the attacker first got onto the systems; which merchants, POS vendors or banks were involved; whether the million records are distinct cards; whether acquirers, card brands or merchants have been told; whether any fraud has been tied to the data.

The numbers, and what they count

FigureWhat it countsSource
782Compromised POS systems listed in the carding panel, each with its Windows version and city and countryCybernews, via IT Finanzmagazin
677Of those systems, in BrazilCybernews, via TechRadar
22In the United StatesCybernews, via TechRadar
8In Russia (the other 75 are spread across further countries)Cybernews, via TechRadar
20Countries (Cybernews's headline; some coverage says "more than 20")Cybernews
1 million+Card records in the panel. Not stated whether duplicates were removed, so this is not a count of distinct cardholdersCybernews, via TechRadar and IT Finanzmagazin
1 year 9 months+How long the affected systems had gone without the fix when the server was foundCybernews, via Secure Blink

The panel records reportedly held the card number, expiry date, bank identification number (BIN), issuing country and bank, card type and brand, and the date each record was taken. No source we read says card security codes or PINs were present. Cybernews says the risk to cardholders depends on each issuing bank's fraud detection and cardholder protection.

How the attack worked (defensive view)

CVE-2024-49138 is a local privilege escalation: it turns a normal user's foothold into SYSTEM rights. It does not let anyone in from the network. So there were two steps, and only the second is described: the attacker first got some way to run code on each POS system (not stated in any coverage we read), then used the CLFS flaw to take full control and install a remote access trojan that read card data as transactions passed through. Cybernews says the attacker adapted public proof-of-concept code, which means the skill needed was moderate. The machines had simply not been updated.

This is the classic POS "RAM scraping" pattern: when a Windows POS application handles the clear card number, malware with enough rights can read it from memory. Patching closes this route to SYSTEM. Encrypting the card in the card reader removes the clear number from the Windows host altogether.

Useful next, if this was relevant to you

Showing 1 of 3: CISO Readiness Scorecard

What security leaders should do this week

  • Prove the December 2024 fix is on every POS system. Pull the Windows build of every POS host, back-office server and store server, and confirm each is at or past the December 2024 cumulative update listed for its version in Microsoft's advisory. Don't trust the patch report alone: check the build number on the machine. PCI DSS v4.0.1 requirement 6.3.3 expects critical patches within one month of release.
  • Find unsupported Windows builds. POS estates often run old or embedded Windows versions that no longer get updates, or that a POS vendor has not certified for new patches. List them, ask the vendor for a patched or supported build, and isolate what cannot be fixed. Our vulnerability prioritizer and KEV checker help put exploited flaws like this first.
  • Allow-list what runs on POS. A POS system runs a small, fixed set of programs. Application allow-listing (for example Windows Defender Application Control or AppLocker) blocks an unknown trojan even if a privilege-escalation bug is missed.
  • Segment the POS estate. POS systems should talk only to the payment and back-office services they need, with no general internet access and no path from the corporate or guest network. That limits both the first foothold and where stolen data can go.
  • Take clear card data off the Windows host. With a validated point-to-point encryption (P2PE) solution, the card is encrypted in the card reader, so the Windows POS host never holds the clear card number; tokenisation keeps it out of storage afterwards. This is the control that makes RAM scraping pointless, and it also shrinks your PCI DSS scope.
  • Look for POS malware, not just patch gaps. Have endpoint detection on POS hosts alert on new services, unsigned programs, processes reading the POS application's memory and unexpected outbound connections from store systems.
  • If you find a compromise, follow your PCI DSS incident plan. Contain without wiping (preserve evidence), call your acquirer promptly (PCI DSS 12.10.1 expects your plan to cover notifying the payment brands and acquirers), and expect a PCI forensic investigator. Our incident response readiness scorecard shows whether your plan covers it, and the PCI DSS compliance guide covers scope and requirements.

Timeline

DateEventSource
10 Dec 2024Microsoft fixes CVE-2024-49138 in the December security updatesMicrosoft
10 Dec 2024CISA adds CVE-2024-49138 to the Known Exploited Vulnerabilities catalog; federal deadline 31 Dec 2024CISA KEV
Aug 2026Cybernews finds the attacker's server open on the internet; the affected systems still lack the fixCybernews, via IT Finanzmagazin
31 Aug 2026The server is no longer reachableCybernews, via TechRadar
8 Sep 2026Cybernews reports the find to Brazil's national CERT (CTIR)Cybernews, via Secure Blink
18 Nov 2026First coverage of the Cybernews report we foundIT Finanzmagazin
19 Nov 2026TechRadar reports the researchTechRadar

Where the reports disagree

  • How many systems: 782 in the panel (Cybernews, as reported by TechRadar and IT Finanzmagazin); some outlets round to "more than 700".
  • How many countries: 20 in Cybernews's headline; "more than 20" or "at least 20" elsewhere.
  • Records or cards: outlets use "records", "cards" and "cardholders" for the same million, and none states a de-duplication method.

Is Microsoft at fault?

This is not a breach of Microsoft. CVE-2024-49138 is a Windows flaw Microsoft fixed in December 2024; the victims were merchants whose POS systems had not been updated. Our Microsoft Breach Index entry lists it as a vulnerability, not a breach.

Frequently asked questions

What happened with the 782 POS terminals?

Cybernews researchers say they found an attacker's server left open on the internet in August 2026. It held malware source code, exploitation tools and a carding panel (the back office where stolen card data is stored and sorted) called "VINY JUNIOR TRILHAS". According to Cybernews, the panel listed 782 compromised point-of-sale systems and held more than one million payment card records captured as transactions went through.

Which countries were affected?

Cybernews counts 677 of the 782 systems in Brazil, 22 in the United States and 8 in Russia, with the rest spread across other countries; its headline says 20 countries and some coverage says more than 20. Coverage of the report says Brazilian banks' cards were the main target.

What is CVE-2024-49138?

A Windows Common Log File System (CLFS) driver elevation-of-privilege flaw. Microsoft fixed it in the December 2024 security updates (10 December 2024), and CISA added it to its Known Exploited Vulnerabilities catalog the same day, meaning it was already being exploited. It lets someone who can already run code on a machine as a normal user gain SYSTEM rights. It is not a way in by itself.

How did the attackers get into the POS systems?

Not stated. CVE-2024-49138 needs an existing low-privilege foothold on the machine, and none of the reporting we could read says how the attacker got that first access. Cybernews says the attacker adapted publicly available proof-of-concept code for the flaw rather than writing a new exploit.

Is it 1 million unique cards?

Not clear. Coverage describes "more than one million" card records or cards found in the panel, but none says whether duplicates were removed. Treat it as Cybernews's count of records in the panel, not a confirmed count of distinct cardholders.

What card data was stolen?

According to Cybernews, the panel held card numbers, expiry dates, the bank identification number (BIN), issuing country and bank, card type and brand, and the date each record was taken. It also listed each terminal's Windows version and city and country. No source we read says card security codes, PINs or cardholder names were in the panel.

Who is behind it?

Unconfirmed. Cybernews assesses the operator as Brazilian from the language of documents on the server; that is an assessment, not an attribution, and no group has been named.

Were banks or card brands told?

The only notification reported is Cybernews telling Brazil's national CERT (CTIR) on 8 September 2026, after the server went offline on 31 August. We found no report of acquirers, card brands or the affected merchants being notified.

What should retailers do now?

Confirm every Windows POS system has the December 2024 updates or later, find unsupported Windows builds and get them replaced or isolated, lock POS systems to an allow-list of approved software, segment them from the rest of the network, and move to point-to-point encryption or tokenisation so a Windows POS system never holds the clear card number. If you find signs of compromise, follow your PCI DSS incident plan and call your acquirer.

Was Microsoft breached?

No. This is a vulnerability in Windows that Microsoft fixed in December 2024; the campaign targeted merchants' unpatched POS systems.

Sources

Rank the exploited flaws on your estate first
Put KEV-listed, exploited bugs like CVE-2024-49138 ahead of the long tail, starting with systems that touch card data.
Open the vulnerability prioritizer
Take this with you
Confirmed vs not yet known · The numbers, and what they count · How the attack worked (defensive view) · What security leaders should do this week · Timeline · Where the reports disagree

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro