VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/influxdata/influxdb: vulnerability history, versions and safety

github.com/influxdata/influxdb is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from May 2021 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/influxdata/influxdb vulnerabilities

Vulert verdict on github.com/influxdata/influxdb v1.13.1 i

Updated on 23 Oct 2026

Action needed: v1.13.1 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.13.1 — affected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 31,765 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/influxdata/influxdb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.11.1-0.20261014193620-3a736253566f 14 Oct 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20261012114811-fd854d8a3a2b 12 Oct 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260925194728-972c26a1ddbb 25 Sep 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260923193709-0566ba1bb2dc 23 Sep 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260921125036-d6ecda8fb43e 21 Sep 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260825203742-8a2663add71e 25 Aug 2026 C1 M1 U1 MIT Yes Details →
v1.13.1 20 Aug 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260727181529-8d81a1e36d73 27 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260723175037-e30b5b226075 23 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.13.0 23 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260723175027-c82228df36b5 23 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260721210913-3d4d4afce490 21 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260720190730-798e8bfc4e80 20 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260717225737-4bb28843ea87 17 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260715212938-1784768dbf1e 15 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260715185630-f77fdde83b7d 15 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260709205813-3cbe3e62dc2e 09 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260708154227-e14f9ace15d0 08 Jul 2026 C1 M1 U1 MIT Yes Details →
v1.12.5-0.20260529173023-7d8b4e6200f6 29 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260528195252-4990347fb802 28 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260522212436-4300c5b65093 22 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260522124601-6bf8bab41650 22 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260521191251-4f4a60ec06a4 21 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260521182400-8c1c2f5e6600 21 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260521044913-0c9304960cb7 21 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260521014148-0c8d79895edb 21 May 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260514201717-7fe7206e8429 14 May 2026 C1 M1 U1 MIT Yes Details →
v1.12.5-0.20260430192032-4c55d97ae13f 30 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260430185009-ca6a2f48cb68 30 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260430180016-fe483833a6ce 30 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260429190431-3648bb08eb3c 29 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260427154010-4d9447b74a2a 27 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.12.4 09 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.12.4-0.20260409200916-f9befe3459b6 09 Apr 2026 C1 M1 U1 MIT Yes Details →
v1.12.3 27 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-rc.0.0.20260227181538-f3d5cb68ab25 27 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260227170040-37b31006c20f 27 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-rc.0.0.20260219224155-6a3b02cac4f9 19 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260219224142-3b3069ef7a01 19 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260219220120-8774641f85be 19 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-rc.0.0.20260219215833-5e9d85c972f2 19 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260219213101-381fd2d9de3a 19 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260217124239-df00c94e374c 17 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20260213171404-ba705ec658ab 13 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-rc.0 13 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260213162545-945caaf26fab 13 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20260209203302-d65673b1f534 09 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260209201047-d7f79a029ce9 09 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260202194427-093bd3f50a20 02 Feb 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260128224112-85353b3791eb 28 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260128174146-f8351ea57a13 28 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260116222421-c836ac271b7d 16 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260114235236-e5293b741c87 14 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20260112124131-8ca840ffec5e 12 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260109212052-17e70503839d 09 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260109055010-a11657689928 09 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260108054338-6298d5aab012 08 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20260107173253-1a6880b283a3 07 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260107160334-e326f1123d7e 07 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20260106220655-e3b058616c9a 06 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260106211436-6c27c0c69da0 06 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20260106185543-7050b3dd6623 06 Jan 2026 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251223202930-8c9b85043bff 23 Dec 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251223190815-abd617f7cd18 23 Dec 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251209175114-362217b3c142 09 Dec 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251120230358-249312139982 20 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20251120215720-32d8b002d8d4 20 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251119212157-1f5c2b8422da 19 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251107221353-6783a6c9bc71 07 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251107170048-22da7268ba46 07 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.11.10-0.20251103145638-4090a5eb4c16 03 Nov 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20251031200811-542ce7f68409 31 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251030201539-e30bad581d63 30 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251010145342-310d97a04f8a 10 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20251006205616-55b7fb5e1bda 06 Oct 2025 C1 M1 U1 MIT Yes Details →
v0.0.0-20251006190849-803e9487f5e4 06 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251006190849-803e9487f5e4 06 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20251003214735-63498cab4e5b 03 Oct 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20250926221123-bd3eb349a409 26 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20250925140352-c168cc5aca39 25 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250924175017-a02ee8e978b0 24 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.11.9 24 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.11.9-0.20250924123840-8c27c12a507f 24 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20250918153054-0a4c903b47cf 18 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.11.9-0.20250916195415-d1d871215488 16 Sep 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250820223409-7ca78d1342c4 20 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.11.9-0.20250820172307-a1232c5ac879 20 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250820172211-6df8bdbdbecd 20 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.12.3-0.20250820113518-63eb126e55d9 20 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.12.2-0.20250806231218-a54cef740214 06 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.12.2 05 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.12.2-0.20250805202213-95e86be3f4a1 05 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250805195249-22bec4f046a2 05 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.12.2-0.20250801214830-f4116199c3f9 01 Aug 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250725015441-0f570879443f 25 Jul 2025 C1 M1 U1 MIT Yes Details →
v1.11.9-0.20250624221033-cf7bb865741b 24 Jun 2025 C1 M1 U1 MIT Yes Details →
v1.12.1 24 Jun 2025 C1 M1 U1 MIT Yes Details →
v1.12.1-0.20250624221007-32c046b5aefe 24 Jun 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250618191500-4378e857441a 18 Jun 2025 C1 M1 U1 MIT Yes Details →
v1.11.1-0.20250617144033-8ef2aca1ca70 17 Jun 2025 C1 M1 U1 MIT Yes Details →
v1.12.1-0.20250603140552-0fdb6adcb245 03 Jun 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250602225159-7437f275ff88 02 Jun 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250602175954-c07e23714266 02 Jun 2025 C1 M1 U1 — Yes Details →
v1.12.1-0.20250527220009-2a0353ffd240 27 May 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250527215520-1fbe31908074 27 May 2025 C1 M1 U1 — Yes Details →
v1.12.1-0.20250506205630-f738344a81a9 06 May 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250506204239-66f4dbeaadb4 06 May 2025 C1 M1 U1 — Yes Details →
v1.10.9 25 Apr 2025 C1 M1 U1 — Yes Details →
v1.10.9-0.20250425125928-f1c354d93265 25 Apr 2025 C1 M1 U1 — Yes Details →
v1.10.9-0.20250423141527-469192fdb584 23 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.9-0.20250422194504-bf8374320dd0 22 Apr 2025 C1 M1 U1 — Yes Details →
v1.12.1-0.20250422194459-f8635640ccec 22 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250418221819-62e803e673ac 18 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250418185304-f61a0826183b 18 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250417170733-53329a3ad34a 17 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250408173521-e984a226f247 08 Apr 2025 C1 M1 U1 — Yes Details →
v1.12.0 08 Apr 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250321183426-05e543344d7b 21 Mar 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250321172438-77d6f20894b9 21 Mar 2025 C1 M1 U1 — Yes Details →
v1.11.1-0.20250305205906-d8bcbd894c10 05 Mar 2025 C1 M1 U1 — Yes Details →

The newest 120 of 2,774 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/influxdata/influxdb

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-20933: Improper Authentication in InfluxDB 9.8 critical 1.7.6 18 May 2021
CVE-2018-17572: InfluxDB Reflected Cross-site Scripting 4.8 medium 0.9.6 24 May 2022
CVE-2019-20933: Improper Authentication in InfluxDB N/A unrated 1.7.6 21 Aug 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/influxdata/influxdb

Is github.com/influxdata/influxdb safe to use?

Vulert records 3 vulnerabilities for github.com/influxdata/influxdb in Go: 1 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/influxdata/influxdb's Vulert package health score?

Vulert scores github.com/influxdata/influxdb 86/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/influxdata/influxdb affected?

Yes. v1.13.1, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/influxdata/influxdb should I use?

v1.13.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/influxdata/influxdb have?

3 vulnerabilities are recorded for github.com/influxdata/influxdb in the Go ecosystem: 1 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/influxdata/influxdb vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/influxdata/influxdb in the last 12 months, and the oldest entry in this database dates to 18 May 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/influxdata/influxdb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/influxdata/influxdb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/influxdata/influxdb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.