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

CVE-2026-27877

MEDIUM

CVE-2026-27877 is a medium-severity (CVSS 6.5) CWE-312 vulnerability in github.com/grafana/grafana. O3 Security confirms whether CVE-2026-27877 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Public dashboards discloses all direct mode datasources

Also known asBIT-grafana-2026-27877GHSA-3q27-7qjq-p9c5GO-2026-5095
Published
Mar 27, 2026
Updated
Jul 31, 2026
Affected
6 pkgs
Patched
1 / 6
Exploits
None indexed

Real-World Exposure

6 pkgs affected
🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana

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

When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards.

No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-sources as far as possible to improve your deployments' security.

Affected Packages

6 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafana9.3.0No fix
🐹Gogithub.com/grafana/grafana12.0.0No fix
🐹Gogithub.com/grafana/grafana12.2.0No fix
🐹Gogithub.com/grafana/grafana12.3.0No fix
🐹Gogithub.com/grafana/grafana12.4.0No fix
🐹Gogithub.com/grafana/grafana1.9.2-0.20221116104934-4ee83a5f2bf4&&< 1.9.2-0.20260325055210-3522153e07b41.9.2-0.20260325055210-3522153e07b4

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

    No patched version of github.com/grafana/grafana has shipped for CVE-2026-27877 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  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 CVE-2026-27877 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 CVE-2026-27877. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-sources as far as possible to improve your deployments' security.
O3 Security · Impact-Aware SCA

Is CVE-2026-27877 in your dependencies?

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