dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-53523

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.0.0 to before version 2.2.0, the getRedirectURL function in oauth2.go:22-29 constructs the OAuth2 callback URL by concatenating the request's Host header with a fixed path, with zero validation of the Host header. This can result in host header injection. This issue has been patched in version 2.2.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Nezha Monitoring versions 1.0.0 through before 2.2.0 contain a host header injection vulnerability in the getRedirectURL function (oauth2.go:22-29). The function constructs the OAuth2 callback URL by directly concatenating the incoming request's Host header with a fixed path, without any validation or sanitization. An attacker can manipulate the Host header to inject arbitrary hosts into the OAuth2 redirect URL, potentially enabling phishing attacks or theft of authorization codes/tokens.

MitigationUpgrade to Nezha Monitoring version 2.2.0 or later which includes proper validation of the Host header. If immediate patching is not possible, implement host allow-listing at the web server or application level to validate the Host header against trusted domains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Nezha Monitoring version
    Run 'nezha --version' or check the Docker image tag/binary version used in your deployment. If using a package manager, check with 'dpkg -l nezha' or 'rpm -qi nezha' depending on your OS.
    Affected if The version displayed is 1.0.0 or higher but lower than 2.2.0 (for example, 1.5.3, 2.0.1, 2.1.9 would all be affected).
  2. Check if OAuth2 authentication is configured
    Examine your Nezha configuration file (commonly config.yml or similar in the installation directory) for OAuth2-related settings under an 'oauth2' or 'login' section, or check environment variables if using Docker.
    Affected if OAuth2 login is enabled and configured with a provider (such as GitHub, Google, or other OAuth2 providers). If OAuth2 is not enabled, the vulnerable code path may not be exercised.
  3. Verify the getRedirectURL function processes requests
    Review server logs or network traffic to confirm OAuth2 callback requests are being handled by your Nezha instance. The vulnerability is triggered when a user initiates OAuth2 login and the callback URL is constructed.
    Affected if Your Nezha instance handles OAuth2 login flows and constructs callback URLs using the incoming Host header without additional validation at a reverse proxy level.

You are affected if your Nezha Monitoring version is 1.0.0 or higher but lower than 2.2.0 AND you have OAuth2 authentication enabled, allowing attackers to manipulate the redirect URL via the Host header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Nezha Monitoring version 2.2.0 or later which includes proper validation of the Host header. If immediate patching is not possible, implement host allow-listing at the web server or application level to validate the Host header against trusted domains.

Recommended fix High confidence

2.2.0

  1. 1. Back up the current Nezha Monitoring installation and its configuration data
  2. 2. Download Nezha Monitoring version 2.2.0 from the official GitHub repository or release channel
  3. 3. Upgrade the existing installation to version 2.2.0 following the standard upgrade procedure for your deployment method (Docker, binary, or package manager)
  4. 4. Verify the fix by reviewing oauth2.go to confirm the getRedirectURL function now includes proper Host header validation
  5. 5. Test the OAuth2 login flow to ensure the callback URL is correctly constructed and no open redirect occurs

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53523 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data