How severe is CVE-2019-20933?

CVE-2019-20933 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-20933?

CVE-2019-20933 affects the following packages: github.com/influxdata/influxdb (Go). Ecosystems affected: Go.

How do I fix CVE-2019-20933?

Update github.com/influxdata/influxdb to version 1.7.6 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2019-20933 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2019-20933, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-20933?

CVE-2019-20933 has an EPSS (Exploit Prediction Scoring System) score of 93.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2019-20933?

A Nuclei detection template exists for CVE-2019-20933, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-20933 published, and has it been updated?

CVE-2019-20933 was published on November 19, 2020 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

CVE-2019-20933

CRITICAL

Improper Authentication in InfluxDB

Also known asGHSA-2rmp-fw5r-j5qvGO-2022-0780

Published

Nov 19, 2020

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

93.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

Blast Radius

1 pkg affected

🐹github.com/influxdata/influxdb

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/influxdata/influxdb`	all versions	1.7.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

InfluxDB before 1.7.6 has an authentication bypass vulnerability in the …

github.comGithubApr 2021

Frequently Asked Questions

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).

O3 Security · Impact-Aware SCA

Is CVE-2019-20933 in your stack?

O3 detects CVE-2019-20933 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works