Quick answer
Password spraying is an attack that tries a small number of common passwords, such as Summer2026! or the company name plus a year, against many accounts at once. Trying only one or two passwords per account avoids lockout thresholds, and in any large organization at least one person is usually using a predictable password.
On this page
How It Works
The attacker first builds a list of valid usernames from LinkedIn, email formats, previous breaches or username enumeration flaws in login pages. They then try one likely password across every account, wait for lockout counters to reset, and try the next. Targets are anything that accepts a username and password from the internet: Microsoft 365 and other cloud identity providers, VPN portals, Outlook Web Access, Citrix and remote desktop gateways. Spraying is slow and quiet by design, and it is spread across many source IP addresses to avoid simple blocking.
Why It Matters
A single valid password on an account without MFA gives an attacker a foothold, and legacy authentication protocols or forgotten portals often let a password through even when MFA is enforced elsewhere. State-sponsored and criminal groups routinely use spraying against cloud tenants as a first step.
How to Test for It
- Identify every internet-facing login: identity provider, VPN, webmail, remote access and legacy protocols.
- Check whether any of them accept a password without MFA, including legacy authentication paths.
- Run an authorized, carefully throttled spray using seasonal and company-themed passwords to measure exposure without locking accounts out.
- Check whether the spray was detected and alerted on, and how quickly.
- Test whether login pages reveal which usernames are valid.
How to Reduce the Risk
Enforce MFA on every external login and block legacy authentication, ban common and company-specific passwords with a custom banned-password list, enable smart lockout that distinguishes attackers from users, alert on many failed logins across many accounts from one source or pattern, and move towards passwordless and phishing-resistant sign-in.
Regulatory and Framework Context
In the US, CISA and the FBI have issued joint advisories describing password spraying by nation-state actors against cloud tenants, and NIST SP 800-63B recommends screening passwords against lists of commonly used and compromised values.
Being exploited now
Threat Radar →The latest related vulnerabilities confirmed as exploited in the wild.
- CVE-2026-76460·2 months ago·IdentityCisco Identity Services EngineCisco Identity Services Engine Incorrect Use of Privileged APIs VulnerabilityEPSS 75.6%
- CVE-2026-56155·4 months ago·IdentityMicrosoft Active Directory Federation ServicesMicrosoft Active Directory Federation Services Insufficient Granularity of Access Control VulnerabilityEPSS 0.35%
Latest intel on this topic
- When an AI Agent Goes Wrong, Can You Stop It?The Hacker News · November 13, 2026
- gospray - Simple LDAP bind-based password spray toolEmbrace The Red · September 18, 2022
Updated hourly from the daily briefing.
Common questions
What is the difference between password spraying and brute force?
Brute force tries many passwords against one account and triggers lockouts. Spraying tries a few passwords against many accounts, staying under lockout thresholds.
Is password spraying the same as credential stuffing?
No. Credential stuffing replays username and password pairs leaked from other breaches. Spraying guesses common passwords without knowing any real ones.
For testers: finding write-ups
How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.
Change log
- November 13, 2026First published.