Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-xxxw-3j6h-q7h6

MEDIUMFix: grafana/grafana-plugin-sdk-go@aaa26d1

GHSA-xxxw-3j6h-q7h6 is a medium-severity (CVSS 5.9) CWE-522 vulnerability in github.com/grafana/grafana-plugin-sdk-go. O3 Security confirms whether GHSA-xxxw-3j6h-q7h6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Grafana plugin SDK Information Leakage

Also known asCVE-2024-8986GO-2024-3140
Published
Sep 19, 2024
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/grafana/grafana-plugin-sdk-go

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

The grafana plugin SDK bundles build metadata into the binaries it compiles; this metadata includes the repository URI for the plugin being built, as retrieved by running git remote get-url origin.

If credentials are included in the repository URI (for instance, to allow for fetching of private dependencies), the final binary will contain the full URI, including said credentials.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafana-plugin-sdk-goall versions0.250.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana-plugin-sdk-go. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/grafana/grafana-plugin-sdk-go to 0.250.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxxw-3j6h-q7h6 is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-xxxw-3j6h-q7h6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xxxw-3j6h-q7h6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The grafana plugin SDK bundles build metadata into the binaries it compiles; this metadata includes the repository URI for the plugin being built, as retrieved by running `git remote get-url origin`. If credentials are included in the repository URI (for instance, to allow for fetching of private dependencies), the final binary will contain the full URI, including said credentials.
O3 Security · Impact-Aware SCA

Is GHSA-xxxw-3j6h-q7h6 in your dependencies?

O3 detects GHSA-xxxw-3j6h-q7h6 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.