VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/grafana/grafana-infinity-datasource: vulnerability history, versions and safety

github.com/grafana/grafana-infinity-datasource is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 81 releases, first recorded in Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded 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/grafana/grafana-infinity-datasource vulnerabilities

Vulert verdict on github.com/grafana/grafana-infinity-datasource v0.6.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Widely used
  • 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 v0.6.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 11 Aug 2025 i
  • Highest CVSS 5.0 i
  • With no published fix 0 i
  • Stars 1,086 i
  • Last release 65 months ago i
  • Licence Apache-2.0 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/grafana/grafana-infinity-datasource, 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.4.2-0.20261022035150-5d0a36c5510a 22 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20261021021805-2d6f1f678ee9 21 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261021021805-2d6f1f678ee9 21 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261020221634-56d49a42ae8f 20 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20261019165214-5115bbfeec90 19 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261019165214-5115bbfeec90 19 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261015220143-9573ccbbd682 15 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261008100740-bc50025ac4be 08 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20261005201744-574fcc053a62 05 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261005201744-574fcc053a62 05 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20261001150756-4ef0752339f8 01 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20261001150756-4ef0752339f8 01 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260923003801-79f08dff4bce 23 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260825115023-26f314c8792d 25 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260821101148-1ef23ad5f809 21 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260811182513-90436e282d02 11 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260811182513-90436e282d02 11 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260722164250-683f8833617c 22 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260722164250-683f8833617c 22 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260720182906-c69eae205861 20 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260720182906-c69eae205861 20 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260623155744-22a829cec2dc 23 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260623155744-22a829cec2dc 23 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260622100817-8d01502f77bb 22 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260618142931-cb950e1984ac 18 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260618142931-cb950e1984ac 18 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260617080644-0db95011eb71 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260617080644-0db95011eb71 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260409090748-7e2723e5d3b0 09 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260408084244-5e8365b7ff64 08 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260313162038-8c6ff615fba0 13 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260312122541-42bdfe241a03 12 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260302163411-65a171f47445 02 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260302163411-65a171f47445 02 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260224112816-b40dbb154f18 24 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260220140627-9b228b5aab8c 20 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260210131228-e3df4bcded96 10 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260210131228-e3df4bcded96 10 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260115111631-3ab73ef568a4 15 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20260115111631-3ab73ef568a4 15 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20251118151847-d7822ddce203 18 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20251106141609-b357223af913 06 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20251027125053-b990dd405474 27 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20251017094730-1aaf84621d31 17 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250926153119-390b579fc5f6 26 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250923103914-f441d7893a0b 23 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250923103914-f441d7893a0b 23 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250912103938-2abc00b3f5f6 12 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250829102945-43a59ffaae35 29 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250811104410-141c6846dc49 11 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250731100004-9c736aa21b3a 31 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250731100004-9c736aa21b3a 31 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250728104636-4cb8379d1124 28 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250728104636-4cb8379d1124 28 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250602105900-68039270a410 02 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250529103438-266e6e122556 29 May 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20250516103826-f179661b6461 16 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250508172850-e1c0cfab2adf 08 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250324130347-36ba22348926 24 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250311115831-a8418e3a660a 11 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20241021091824-861f06b8cb22 21 Oct 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240801164415-a7104d1fca35 01 Aug 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240627114712-a944ad43e48c 27 Jun 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240624124024-770992939133 24 Jun 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240521125256-e2c95fe71a0d 21 May 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240520140900-ce8d94959f5e 20 May 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240417154537-17ab20b38dbd 17 Apr 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240313084809-a37851f29cea 13 Mar 2024 M1 U1 Apache-2.0 Yes Details →
v1.4.2-0.20240223140143-fa5a32e40d9e 23 Feb 2024 M1 U1 Apache-2.0 Yes Details →
v0.6.1 10 May 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0 18 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha10 18 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha9 15 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha8 13 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha7 11 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha6 11 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha5 11 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha4 11 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha3 18 Dec 2020 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha2 19 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.6.0-alpha1 19 Nov 2020 M1 U1 Apache-2.0 Yes Details →

All 81 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/grafana/grafana-infinity-datasource

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-8341: Grafana Infinity Datasource Plugin SSRF Vulnerability 5.0 medium 1.4.2-0.20250731100004-9c736aa21b3a 04 Aug 2025
CVE-2025-8341: SSRF Vulnerability in Grafana Infinity Datasource Plugin N/A unrated 1.4.2-0.20250731100004-9c736aa21b3a 11 Aug 2025

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/grafana/grafana-infinity-datasource

Is github.com/grafana/grafana-infinity-datasource safe to use?

Vulert records 2 vulnerabilities for github.com/grafana/grafana-infinity-datasource in Go: 0 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/grafana/grafana-infinity-datasource's Vulert package health score?

Vulert scores github.com/grafana/grafana-infinity-datasource 77/100, which reads as in good shape. 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/grafana/grafana-infinity-datasource affected?

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

Which version of github.com/grafana/grafana-infinity-datasource should I use?

v0.6.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/grafana/grafana-infinity-datasource have?

2 vulnerabilities are recorded for github.com/grafana/grafana-infinity-datasource in the Go ecosystem: 0 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/grafana/grafana-infinity-datasource vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/grafana/grafana-infinity-datasource in the last 12 months, and the oldest entry in this database dates to 04 Aug 2025. 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/grafana/grafana-infinity-datasource 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/grafana/grafana-infinity-datasource for upcoming vulnerabilities?

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