Is CVE-2026-47268 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47268 being exploited in the wild.

How severe is CVE-2026-47268?

Medium severity, with a CVSS score of 6.4, published 12 June 2026.

Which products and versions are affected?

github.com/naiba/nezha (Go) SEMVER:introduced=0.20.0; github.com/nezhahq/nezha (Go) >= 0.20.0, = 0.20.0, < 2.0.10; NezhaHQ Nezha Monitoring 0.20.0 to < 2.0.10.

Is there a fix for CVE-2026-47268?

Yes. github.com/nezhahq/nezha (Go): upgrade to 2.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47268 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-47268?

Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha Dashboard or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47268: Nezha Monitoring SSRF in DDNS webhook configuration

Q: Is there a fix for CVE-2026-47268?

Yes. github.com/nezhahq/nezha (Go): upgrade to 2.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47268 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-47268?

Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha Dashboard or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47268 · Severity: medium · CVSS 6.4 · Published 2026-06-12

Nezha Monitoring is a tool used for managing and monitoring servers and websites. A security flaw allows users with basic dashboard access to trick the monitoring server into sending unauthorized web requests to internal systems or private network services. This could allow an attacker to interact with internal tools that are not supposed to be accessible from the internet, potentially leading to unauthorized configuration changes or data exposure within the private network.

Technologies: github.com/nezhahq/nezha (Go), NezhaHQ Nezha Monitoring. Vendors: Go, NezhaHQ.

Quick answers

Is CVE-2026-47268 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47268 being exploited in the wild.
How severe is CVE-2026-47268?: Medium severity, with a CVSS score of 6.4, published 12 June 2026.
Which products and versions are affected?: github.com/naiba/nezha (Go) SEMVER:introduced=0.20.0; github.com/nezhahq/nezha (Go) >= 0.20.0, < 2.0.10, SEMVER:introduced=0.20.0,fixed=2.0.10; NezhaHQ Nezha Dashboard >= 0.20.0, < 2.0.10; NezhaHQ Nezha Monitoring 0.20.0 to < 2.0.10.
Is there a fix for CVE-2026-47268?: Yes. github.com/nezhahq/nezha (Go): upgrade to 2.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47268 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47268?: Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha Dashboard or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/nezhahq/nezha (Go): upgrade to 2.0.10 or later
```
go get github.com/nezhahq/nezha@v2.0.10
```

Technical details

A blind Server-Side Request Forgery (SSRF) vulnerability exists in Nezha Monitoring's DDNS (Dynamic DNS) profile management. Authenticated users can create or update DDNS profiles with a 'webhook' provider and specify arbitrary URLs, HTTP methods, headers, and request bodies. Unlike the application's notification webhooks, the DDNS webhook implementation in `pkg/ddns/webhook/webhook.go` lacks SSRF protections, failing to validate IP ranges or restrict loopback/internal network access. When a DDNS update is triggered—either via the API or an agent IP report—the dashboard process executes the configured request using `utils.HttpClient`. This allows an attacker to target internal services, though the response body is not returned to the user. The issue is fixed in version 2.0.10.

Affected products

NezhaHQ Nezha Monitoring 0.20.0 to < 2.0.10

Identifiers

CVE-2026-47268
GHSA-6x26-5727-rrm9
GO-2026-5194

Timeline

2026-05-19: advisory: GitHub Security Advisory published
2026-06-12: disclosed: NVD publication date
2026-06-12: patched: Vulnerability patched in version 2.0.10

References

https://github.com/nezhahq/nezha/security/advisories/GHSA-6x26-5727-rrm9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.