Skip to main content
Menu
CVEs

CVE

NginxPulse unauthenticated SQL injection in stats API

NginxPulse 1.5.0 before 1.6.26 is affected; the advisory's range ends at 1.6.24. Setups with access keys (system.accessKeys) configured require an attacker to hold one of those keys. Fixed in 1.6.26.

CVE-2026-129171EUVD-2026-125596

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.6.26
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Published
Last modified
Reference
Last checked
0.41% · 36th percentile
41/100
Default setups
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

NginxPulse 1.5.0 before 1.6.26 contains an unauthenticated sql injection vulnerability that allows remote attackers to append SQL via the id and locationType parameters of /api/stats/:type. Attackers can close the quoted table-name identifier and use error-based output to read database contents, and read or write server files via PostgreSQL superuser functions.

Who should check

Teams running likaia NginxPulse 1.5.0 through 1.6.24, including the official Docker image that bundles PostgreSQL.

“Affected versions: 1.5.0 to 1.6.24”

vul.yulun.ac.cn

cve.now Index

41cve.now Index 41 of 100 · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach10/20Affects Go packages
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 1.6.26.

  • Workaround: Enable the access key feature to prevent anonymous attackers from SQL injection

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129171 (NginxPulse 1.5.0 before 1.6.26 SQL Injection via /api/stats/:type), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129171 (entry last updated 2026-11-13):
Affected:
- Go package github.com/likaia/nginxpulse: from 1.5.0, fixed in 1.6.26
Fixed versions: 1.6.26.
Vendor patches: f9416bea (source: https://www.vulncheck.com/advisories/nginxpulse-1.5.0-before-1.6.26-sql-injection-via-api-stats-type). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- NginxPulse 1.5.0 to 1.6.24 (advisory's affected range; CVE range ends before 1.6.26) (source: https://vul.yulun.ac.cn/20261030/nginxpulse/)
- If access keys (system.accessKeys) are configured, the attacker must hold one of those keys (source: https://vul.yulun.ac.cn/20261030/nginxpulse/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Enable the access key feature to prevent anonymous attackers from SQL injection (source: https://www.vulncheck.com/advisories/nginxpulse-1.5.0-before-1.6.26-sql-injection-via-api-stats-type)
CISA KEV: CVE-2026-129171 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129171 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/likaia/nginxpulse/commit/f9416bea3be892a394cd24a6d4a2afbd8397e926
- https://github.com/likaia/nginxpulse/issues/103
- https://vul.yulun.ac.cn/20261030/nginxpulse/
- https://github.com/likaia/nginxpulse/blob/0d41264ae441ddfcb595551f2e2f374f707dae22/internal/analytics/stats.go#L217-L221
- https://github.com/likaia/nginxpulse/blob/0d41264ae441ddfcb595551f2e2f374f707dae22/internal/analytics/overall_stats.go#L219-L224
- https://www.vulncheck.com/advisories/nginxpulse-1.5.0-before-1.6.26-sql-injection-via-api-stats-type
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129171
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129171"}.

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 17
  • EPSS: 0.41%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 6

  1. Patch
  2. Report
  3. Repository
  4. Repository
  5. Link
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129171

Is CVE-2026-129171 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The /api/stats/:type endpoint allows SQL injection. Error-based output can read database contents and, through PostgreSQL superuser functions, read or write server files.Source: vul.yulun.ac.cn, vulncheck.com

Which versions are affected by CVE-2026-129171?

github.com/likaia/nginxpulse (Go): from 1.5.0 before 1.6.26.Source: cve.now feed data

Am I affected, and how do I check?

The advisory lists NginxPulse 1.5.0 through 1.6.24, and the CVE range runs from 1.5.0 before 1.6.26. Check the installed version, and check whether system.accessKeys is configured, since that setting requires an attacker to hold one of the keys.Source: vul.yulun.ac.cn, vulncheck.com

How do I fix CVE-2026-129171?

Upgrade to NginxPulse 1.6.26, or apply the vendor patch f9416bea. Until then, enable the access key feature, which the vendor says prevents anonymous SQL injection.Source: vul.yulun.ac.cn, vulncheck.com