Skip to main content
Mallory
HighVulnerability

CVE-2025-3648: Count(er) Strike: Data Inference in ServiceNow Now Platform Conditional ACLs

Published Jul 8, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v4
EPSS1.7%77th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-3648CWE-863
Also known ascount(er)_strike

CVE-2025-3648, known as Count(er) Strike, is an authorization flaw in ServiceNow Now Platform conditional Access Control List (ACL) evaluation. Under certain ACL configurations, unauthenticated or authenticated users can submit range-query requests and infer instance data that ACL policy was intended to withhold. The issue can manifest as count-based blind inference, where query behavior reveals whether protected records matching selected conditions exist without necessarily returning the records themselves.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can infer protected instance data without authorization. The exposed information may include sensitive data, and count-based responses can be used as an oracle to progressively determine protected record attributes or the existence of records matching attacker-controlled conditions.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to data-bearing query interfaces and rigorously test conditional ACLs using both unauthenticated and low-privilege authenticated sessions. Implement least-privilege table, row, and field controls, and use Query ACLs, Security Data Filters, and Deny-Unless ACLs where available to prevent unauthorized query-result and count-based inference.

Remediation

Patch, then assume compromise.

Apply ServiceNow's May 2025 security update for CVE-2025-3648 and review the applicable ServiceNow knowledge-base guidance. Upgrade or adopt the Xanadu or Yokohama access-control capabilities where appropriate, including Query ACLs, Security Data Filters, and Deny-Unless ACLs. Review conditional ACL configurations to ensure range queries cannot disclose data or record-existence information to unauthorized sessions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-3648 exploited in the wild?
As of Sep 30, 2026, Mallory has no reports of CVE-2025-3648 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-3648?
As of Sep 30, 2026, Mallory has found no public exploit for CVE-2025-3648.
Is there a patch for CVE-2025-3648?
Apply ServiceNow's May 2025 security update for CVE-2025-3648 and review the applicable ServiceNow knowledge-base guidance. Upgrade or adopt the Xanadu or Yokohama access-control capabilities where appropriate, including Query ACLs, Security Data Filters, and Deny-Unless ACLs.
How severe is CVE-2025-3648?
CVE-2025-3648 has a CVSS v4 score of 8.2 (High) and an EPSS score of 1.7% (77th percentile) as of Sep 30, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.