GHSA-2rmp-fw5r-j5qv is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in github.com/influxdata/influxdb. 2 public exploit references exist, so weaponization risk is real. A fix is available for github.com/influxdata/influxdb — see the affected versions and patch details below.
Improper Authentication in InfluxDB
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2rmp-fw5r-j5qv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/influxdata/influxdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka shared secret).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/influxdata/influxdb | all versions | 1.7.6go get github.com/influxdata/influxdb@v1.7.6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/influxdata/influxdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/influxdata/influxdb to 1.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rmp-fw5r-j5qv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2rmp-fw5r-j5qv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2rmp-fw5r-j5qv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-2rmp-fw5r-j5qv
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-2rmp-fw5r-j5qv -u https://target- Template
- InfluxDB <1.7.6 - Authentication Bypass
- Severity
- critical
- Impact
- An attacker can bypass authentication and gain unauthorized access to the InfluxDB database.
- Remediation
- Update Influxdb to version 1.7.6~rc0-1 or higher.
Template by ProjectDiscovery nuclei-templates (pussycat0x, c-sh0), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-2rmp-fw5r-j5qv in your dependencies?
O3 Security finds GHSA-2rmp-fw5r-j5qv across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.