Check Point CVE-2026-16232: SmartConsole auth bypass exploited, full admin access via unauthenticated token theft, CISA KEV July 25 deadline      HermeticReader CVE-2026-48294: Adobe Chrome extension flaw let a webpage steal WhatsApp messages from 329 million browsers      SharePoint CVE-2026-50522: now confirmed exploited to steal IIS machine keys for permanent token-forging persistence      Check Point CVE-2026-16232: SmartConsole auth bypass exploited, full admin access via unauthenticated token theft, CISA KEV July 25 deadline      HermeticReader CVE-2026-48294: Adobe Chrome extension flaw let a webpage steal WhatsApp messages from 329 million browsers      SharePoint CVE-2026-50522: now confirmed exploited to steal IIS machine keys for permanent token-forging persistence     
CyberSipTM
Intelligence without the noise
Issue No. 92
July 23, 2026
3 items · past 24h
<5 min read
Today's picture

Check Point confirmed active exploitation of CVE-2026-16232, an authentication bypass in the SmartConsole management platform that lets an unauthenticated attacker grab an application login token and take full administrative control of firewall policy. CISA added it to KEV yesterday with a two-day federal deadline. Guardio Labs disclosed HermeticReader, a flaw in the Adobe Acrobat Chrome extension installed in approximately 329 million browsers, where visiting a malicious webpage while signed into WhatsApp Web was enough to silently exfiltrate chat lists, contacts, and message previews without any malware or stolen credentials. Adobe patched it in June but disclosed the vulnerability's full technical details yesterday. And SharePoint CVE-2026-50522, confirmed on CISA KEV alongside the Check Point flaw, is being exploited specifically to steal IIS machine keys, giving attackers the ability to forge authentication tokens that bypass SharePoint's security controls indefinitely.

Today's intelligence
3 items
01 CriticalCheck PointCISA KEV
Check Point SmartConsole has an exploited authentication bypass giving attackers full administrative control of firewall policy
The attacker does not need credentials. They grab a login token from an exposed management server and walk in as a full administrator. Federal agencies have until July 25. Check Point says a handful of customers with management servers directly exposed to the internet are confirmed affected.
CVECVE-2026-16232
CVSS9.1
KEV addedJuly 22, 2026
Fed deadlineJuly 25, 2026
Check Point published its advisory on July 22 covering multiple vulnerabilities in Security Management, Multi-Domain Management, and firewall products. The most urgent is CVE-2026-16232, an authentication bypass in the SmartConsole login process. The vulnerability allows an unauthenticated remote attacker to obtain an application login token and authenticate to the management server with full administrative privileges, enabling modification of security policies and security configurations. Exploitation requires network access to the Management Server IP address in environments that have not restricted Trusted Clients to a specific list of approved IP addresses or subnets. Check Point confirmed active exploitation affecting what the company describes as a handful of customers with management environments directly exposed to the internet. Targeted customers have been privately notified. Check Point released Jumbo Hotfixes for supported versions R81.20, R82, and R82.10 on July 22. The same advisory covers CVE-2026-62144, a second critical authentication bypass in Gateway management that exploits the same configuration precondition. CISA added CVE-2026-16232 to its KEV catalog on July 22 with a federal remediation deadline of July 25, the shortest timeline between KEV addition and deadline this brief has seen in 2026. Check Point has also published indicators of compromise for the attacks.
SmartConsole is the administrative interface through which Check Point security policies are written, deployed, and changed. An attacker with administrative access to SmartConsole can rewrite firewall rules, disable logging, add permitted traffic flows, or silently remove blocks on attacker-controlled infrastructure. A compromised firewall management server does not just mean one compromised device. It means every policy enforced by gateways managed through that server is now under attacker control.
This is Check Point's third vulnerability added to CISA KEV in 2026, following CVE-2026-50751, a critical authentication bypass in Remote Access VPN exploited as a zero-day in May, and CVE-2024-24919, a high-severity information disclosure flaw from 2024. The pattern of authentication bypass vulnerabilities in Check Point's management and access products appearing in KEV across consecutive quarters should factor into risk assessments for environments running this vendor's infrastructure. The three-day federal remediation window set by CISA is the operational signal here. Whatever the standard patch cycle looks like for Check Point management systems, this week is not a standard cycle.
  • Apply the July 22 Jumbo Hotfix for your Check Point Security Management version immediately. The fix is available for R81.20, R82, and R82.10. End-of-service versions are not receiving hotfixes. Review the advisory for compensating controls if you are running an unsupported version.
  • Restrict Trusted Clients in SmartConsole to a specific list of approved IP addresses or subnets. This eliminates the primary exploitation precondition for both CVE-2026-16232 and CVE-2026-62144 by ensuring the management server is not reachable from arbitrary network addresses.
  • Review Check Point's published indicators of compromise for CVE-2026-16232 and check management server access logs for authentication events that did not originate from expected administrator IP addresses, and for any policy changes made since the vulnerability was published on July 22.
An attacker with access to SmartConsole does not have access to one system. They have access to the ruleset governing every system those gateways protect. Two days to patch under CISA's order. Whatever else is on the queue this week, this goes first.
02 HighHermeticReaderAdobe Extension
A flaw in the Adobe Acrobat Chrome extension let a malicious webpage silently steal WhatsApp messages and contacts from 329 million browsers
No malware. No stolen password. No WhatsApp vulnerability. Visiting the wrong page while signed into WhatsApp Web with the Adobe extension active was enough. Adobe patched it in June. The disclosure came yesterday.
CVECVE-2026-48294
NamedHermeticReader
(Guardio Labs)
Installs~329 million
Chrome browsers
PatchedJune 2026
Extension auto-update
Guardio Labs disclosed CVE-2026-48294 yesterday, a vulnerability it named HermeticReader affecting version 26.5.2 of the Adobe Acrobat Chrome extension installed in approximately 329 million browsers. The flaw is a universal cross-site scripting class issue rooted in weak trust boundaries between the extension and web pages it interacts with. Adobe's extension exposed web-accessible pages that accepted JSON data through URL parameters, which Guardio researchers used to inject content into the extension's context. From there, despite WhatsApp Web's Content Security Policy blocking straightforward script injection, they found a more subtle path: the exploit injected an attacker-controlled HTML form into the WhatsApp Web page, moved the live WhatsApp page body into a form option element, and submitted the form to an attacker-controlled server. Because an HTML option element without a value attribute submits its text content, the resulting POST request carried the rendered WhatsApp Web page contents: chat lists, contact names, message previews, profile details, and visible conversation text. The attack required no malware, no phishing for credentials, no WhatsApp vulnerability, no session cookie theft, and no interaction beyond the target visiting a webpage. Guardio disclosed the finding to Adobe, which developed a fix and pushed it through the extension's automatic update mechanism in June, shortly after receiving the report. Adobe assigned CVE-2026-48294 and described it as a UXSS-class cross-origin data disclosure vulnerability. No exploitation in the wild has been confirmed.
WhatsApp Web is used by professionals who also use Adobe Acrobat in their browser workflow, meaning the population of users who had both installed simultaneously is a substantial fraction of the 329 million extension installs. The attack required zero technical sophistication from the attacker beyond hosting a static webpage and waiting for a visit. The victim had to do nothing beyond navigating to a page, which is the bar for phishing links, malicious ads, and compromised legitimate sites. Chat histories and contact lists extracted this way are persistent intelligence, not one-time credential access.
Chrome extensions are a broadly underappreciated browser attack surface. An extension installed across 329 million browsers holds permissions and cross-origin trust relationships that dwarf the footprint of most enterprise software. HermeticReader is not the first high-impact extension flaw this year: earlier in 2026, the ModHeader extension with 1.6 million installs was removed from Chrome and Edge stores after researchers found dormant code capable of encrypting and uploading browsing history to an external server. Organizations that manage browser deployments through enterprise Chrome policies should audit which extensions are permitted, with particular attention to extensions holding broad host permissions or access to web-accessible resources that interact with authenticated sessions.
  • Confirm the Adobe Acrobat Chrome extension has updated past version 26.5.2. Chrome extensions update automatically, but enterprise-managed deployments with extension version pinning may be on an older version. Check chrome://extensions and verify the Adobe Acrobat extension version.
  • Audit enterprise-permitted Chrome extensions for those holding broad host permissions or web-accessible resource access. Extensions with access to all sites combined with exposure to authenticated web applications create exactly the cross-origin trust boundary that HermeticReader exploited.
An extension installed in 329 million browsers had a flaw where visiting the wrong page while signed into WhatsApp sent your conversations to an attacker's server. No malware, no login prompt, no warning. Adobe patched it in June. The disclosure arrived yesterday. Check the extension version.
03 CriticalSharePointMachine Key Theft
SharePoint CVE-2026-50522 is confirmed exploited to steal IIS machine keys, giving attackers permanent token-forging capability that survives patching
Exploiting a remote code execution flaw to steal the machine key is not the same as exploiting it for access. The key gives attackers the ability to forge valid authentication tokens indefinitely, on any IIS server sharing that key, including after the original vulnerability is patched.
CVECVE-2026-50522
CVSS9.8
KEV addedJuly 22, 2026
AffectsSharePoint Server
all on-prem versions
CISA added CVE-2026-50522 to its Known Exploited Vulnerabilities catalog on July 22, confirming active exploitation of a CVSS 9.8 deserialization of untrusted data vulnerability in Microsoft SharePoint Server. CVE-2026-50522 was patched in Microsoft's July 15 Patch Tuesday release. The confirmed exploitation pattern documented by threat intelligence analysts is machine key theft: attackers exploit the remote code execution capability to read the IIS machineKey values from the Web.config file on the compromised SharePoint server. IIS machine keys are used by ASP.NET to encrypt, decrypt, and validate authentication tokens, view state, and session cookies across all applications running on that IIS instance. An attacker who possesses the machine key can forge ViewState or Forms Authentication tokens that IIS will treat as fully valid, allowing the attacker to authenticate as any user, including administrators, without knowledge of their credentials. Crucially, machine keys persist across patch cycles. Patching CVE-2026-50522 closes the remote code execution path, but any machine key already stolen before patching remains valid and usable until it is explicitly rotated. This exploitation pattern places it in the same category as the IIS machine key attacks documented in connection with CVE-2025-50982 earlier this year, where stolen keys were used months after the initial breach to maintain persistent access to patched systems.
This is now the fifth distinct SharePoint CVE confirmed exploited in active attacks since Issue 78 of this brief, with CVE-2026-45659, CVE-2026-32201, CVE-2026-56164, and CVE-2026-58644 preceding it. The machine key theft objective is the critical detail. It means organizations that patched SharePoint after the July 15 release but have not rotated their IIS machine keys may have already lost the persistent access capability the attacker was after. Patching is necessary. Machine key rotation is the additional step that closes the persistence path.
CISA's advisory for the SharePoint exploitation campaign explicitly recommends rotating IIS machine keys and Internet Information Services (IIS) application pool identities as a remediation step alongside patching. This has been documented as the specific post-exploitation objective in multiple SharePoint intrusions this month, meaning it is not a theoretical concern but a confirmed attacker goal. Organizations that patched after July 15 and did not rotate machine keys should treat the keys as potentially stolen regardless of whether they observed a successful intrusion. Machine keys are silent to steal. The theft leaves no user-visible indicator.
  • Apply all July 2026 SharePoint patches immediately, including the July 15 Patch Tuesday updates addressing CVE-2026-50522. If not already done, this is the fifth exploited SharePoint CVE documented in this brief since early July and cannot be treated as a routine cycle item.
  • Rotate IIS machine keys on all SharePoint servers regardless of whether a successful intrusion has been confirmed. Generate new machineKey values in Web.config, redeploy, and recycle IIS application pools. Any machine key that existed before patching should be considered potentially stolen.
  • Review IIS and SharePoint access logs for authentication events using forged tokens: sessions authenticating as high-privilege accounts from unexpected IP addresses, activity during off-hours, or access patterns inconsistent with the account's normal behavior are the signals to hunt for.
Patching removes the entry point. It does not invalidate the key that was already taken. A stolen IIS machine key is a credential that never expires and leaves no authentication log entry when used to forge a token. Patch the CVE. Then rotate the key. In that order, today.
Cross-source standouts
01
The Check Point and SharePoint stories both show that patching the vulnerability is not the same as removing the attacker's capability
Check Point's advisory notes that exploitation allows modification of security policies and security configurations. An attacker who rewrote firewall rules before the patch was applied has persistent access through those rules even after CVE-2026-16232 is hotfixed, because the vulnerability was the door, not the damage. The machine key theft in the SharePoint exploitation makes the same point more explicitly: the stolen key works indefinitely on patched systems. This is the post-patch investigation problem this brief documented with CitrixBleed 2 in Issue 85, where session tokens stolen before patching remained valid after it. Patching and remediation are different activities. Patching closes the mechanism of access. Remediation confirms what was done with that access before it was closed and removes any persistence that survived the patch. In all three cases, the step most organizations skip is the second one.
02
HermeticReader illustrates why browser extensions deserve the same security scrutiny as installed software
The Adobe Acrobat Chrome extension has 329 million installs, which makes it larger than most operating system user bases. An extension at that scale holds broad host permissions across every site a user visits, runs in the same browser process as authenticated sessions, and often persists across years of use with automatic updates that users rarely audit. HermeticReader's specific mechanism, injecting content into an extension's trusted context to harvest data from an adjacent authenticated session, is not unique to Adobe or to WhatsApp. Any extension that interacts with web content and holds access to pages running authenticated sessions creates a potential cross-origin trust boundary. This category of attack does not require a vulnerability in the target application: WhatsApp had no flaw here. It requires only that the extension holding elevated trust has a weakness that an attacker can reach from an untrusted page. Earlier in 2026, the ModHeader extension with 1.6 million installs was pulled from Chrome and Edge stores after researchers found it contained dormant code capable of capturing and exfiltrating browsing history. Two high-profile extension incidents in a single year is not a coincidence. Browser extensions are software running with elevated privilege inside the most sensitive application on most users' devices, and they receive a fraction of the security review that enterprise software gets.
Still watching
Days 2–5
Oracle CPU PeopleSoft CVE-2026-35278 and CVE-2026-35273 (Issue 91 · ShinyHunters active since May) — confirmed exploited across 100-plus organizations. Apply July CPU patches to PeopleSoft immediately. Review HR, payroll, and PII database logs from May 27 onward for unauthorized access.
Day 2
wp2shell CVE-2026-63030 and CVE-2026-60137 (Issue 90 · active exploitation) — attacks confirmed spreading globally since July 19. Verify all WordPress sites on 6.9.5, 7.0.2, or 6.8.6. Hunt for HTTP 207/200 responses to /wp-json/batch/v1 in logs. Inspect upload directories for unexpected PHP files.
Day 5
LegacyHive (Issue 88 · Nightmare Eclipse, no patch) — Windows User Profile Service privilege escalation. No CVE, no fix, working proof-of-concept confirmed on fully patched July systems. Three prior disclosures in this series were exploited before patches arrived.
Day 6
SharePoint four-CVE campaign (Issues 86–87 · CISA, Storm-2603) — CVE-2026-45659, CVE-2026-32201, CVE-2026-56164, and CVE-2026-58644 all exploited. Now add CVE-2026-50522 with machine key theft confirmed. Patch all five, rotate IIS machine keys, enable AMSI in full mode.
Day 7