Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-101089 Overview
CVE-2026-101089 is an information disclosure vulnerability in Nezha, an open-source server monitoring and management platform. Versions prior to 2.2.7 expose the bcrypt-hashed password of authenticated users through the GET /api/v1/profile endpoint. Any authenticated low-privilege user can retrieve their own password hash from the API response. Attackers can then perform offline password cracking without rate limiting, lockouts, or audit trail restrictions. The underlying weakness is categorized as [CWE-522] Insufficiently Protected Credentials.
Critical Impact
Authenticated users can extract bcrypt password hashes through a profile API endpoint, enabling offline cracking attacks against user credentials without detection.
Affected Products
- Nezha monitoring platform versions prior to 2.2.7
- Deployments exposing the /api/v1/profile endpoint to authenticated users
- Self-hosted Nezha dashboards accessible over the network
Discovery Timeline
- 2026-09-27 - CVE-2026-101089 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-101089
Vulnerability Analysis
Nezha exposes a profile retrieval endpoint at GET /api/v1/profile that returns authenticated user attributes. In versions before 2.2.7, the serialized response includes the user's bcrypt-hashed password field. The API does not filter sensitive credential material from the response payload. Any authenticated session, including low-privilege accounts, can access this data path.
Once extracted, the bcrypt hash can be subjected to offline brute-force or dictionary attacks using tools such as hashcat or john. Because cracking occurs offline, server-side defenses including rate limiting, failed login throttling, and audit logging do not apply. Weak or reused passwords can be recovered and leveraged for account takeover or lateral movement across environments where the same credentials are reused.
Root Cause
The root cause is improper output filtering in the profile serializer. The user object persisted in the backing store includes the Password field containing the bcrypt hash. The handler for /api/v1/profile returns the full user structure without applying a data transfer object or field whitelist that excludes credential material. This is a classic Insufficiently Protected Credentials flaw where sensitive storage data crosses the API trust boundary.
Attack Vector
Exploitation requires an authenticated session on the target Nezha instance. The attacker issues an authenticated GET request to /api/v1/profile and parses the JSON response for the password field. The attack is low complexity in terms of request shape but carries elevated attack complexity because the attacker must first obtain valid credentials. Refer to the GitHub Security Advisory GHSA-8jhq-g4gw-rv5f and the VulnCheck advisory for Nezha API information disclosure for additional technical context.
Detection Methods for CVE-2026-101089
Indicators of Compromise
- Authenticated GET requests to /api/v1/profile from unexpected source addresses or user agents
- Response payloads from /api/v1/profile containing a password field with a bcrypt prefix such as $2a$, $2b$, or $2y$
- Account logins from new geographies shortly after profile endpoint access, indicating possible successful offline cracking
Detection Strategies
- Deploy web application firewall or reverse proxy rules that inspect responses from /api/v1/profile for bcrypt hash patterns and alert on matches
- Correlate access to the profile endpoint with subsequent authentication anomalies from the same account
- Review Nezha application logs for high-frequency profile endpoint retrievals that deviate from normal user interface activity
Monitoring Recommendations
- Enable verbose HTTP access logging on the Nezha dashboard and forward logs to a central analytics platform
- Track authentication telemetry for all Nezha user accounts to flag credential-stuffing attempts following profile access
- Monitor for new administrative actions or configuration changes performed shortly after profile endpoint queries
How to Mitigate CVE-2026-101089
Immediate Actions Required
- Upgrade Nezha to version 2.2.7 or later on all deployments
- Force a password reset for all Nezha accounts after upgrading, assuming prior hash exposure
- Restrict network access to the Nezha dashboard using IP allowlists or a VPN until patching is complete
- Audit account inventory and disable unused or stale accounts that could serve as entry points
Patch Information
The fix is included in Nezha release 2.2.7. The upstream project removes the password field from the profile API response. Review the GitHub Security Advisory GHSA-8jhq-g4gw-rv5f for release notes and commit references.
Workarounds
- Place a reverse proxy in front of Nezha that strips the password field from /api/v1/profile JSON responses before returning them to clients
- Enforce strong password policies and unique credentials to limit the value of any hash recovered through offline cracking
- Rotate credentials and invalidate active sessions if there is any evidence of unauthorized profile endpoint access
# Example NGINX response filtering using the sub_filter module
location /api/v1/profile {
proxy_pass http://nezha_backend;
sub_filter_types application/json;
sub_filter_once off;
sub_filter '"password":"$2' '"password":""';
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

