CVE-2026-27480Public exploitNetwork attack vector

Username enumeration via early authentication rejection

Published Feb 21, 2026 · Updated Feb 21, 2026

Timing-based username enumeration in Static Web Server 2.1.0 through 2.40.1 allows remote attackers to identify valid Basic Authentication users. Basic Authentication's check_request function in src/basic_auth.rs returns 401 before bcrypt verification when the supplied username differs, while valid usernames incur password hashing. Basic Authentication must be enabled and reachable; the resulting account list supports targeted password guessing but does not disclose passwords or grant access by itself.

CVSS severity5.3
Medium
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Timing-based username enumeration in Static Web Server 2.1.0 through 2.40.1 allows remote attackers to identify valid Basic Authentication users. Basic Authentication's check_request function in src/basic_auth.rs returns 401 before bcrypt verification when the supplied username differs, while valid usernames incur password hashing. Basic Authentication must be enabled and reachable; the resulting account list supports targeted password guessing but does not disclose passwords or grant access by itself.

The record

CVE
CVE-2026-27480
Published
Feb 21, 2026
Updated
Feb 21, 2026
Vendor
Static Web Server
Product
Static Web Server
Classifications
CWE-204, T1589.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 21, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 21, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 2.1.0, < 2.41.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Static Web Server · Static Web Serverversion=>= 2.1.0, < 2.41.0

Published CVSS scores

5.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-204Observable Response Discrepancy
T1589.001Gather Victim Identity Information: Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo