OpenMeter: SQL injection through meter creation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-8462: 0.51% estimated exploitation activity in the next 30 days; percentile 43.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An authenticated tenant can inject arbitrary SQL through the valueProperty or groupBy fields of POST /api/v1/meters. The injection passes the application's JSONPath validation check and executes against the shared ClickHouse database, which contains event data for all tenants with no row-level security. Any authenticated tenant can read or write every other tenant's metering data. Details openmeter/streaming/clickhouse/utilsquery.go:15 builds a ClickHouse SELECT by interpolating user input with fmt.Sprintf: sqlbuilder.Escape() (go-sqlbuilder v1.40.2) only replaces $ → $$ to prevent collisions with the library's own argument placeholders. It does not escape single quotes. A single quote in the input closes the string literal, and subsequent tokens execute as raw SQL. sb.Build() always returns an empty args slice — the query is never parameterized. The payload must be prefixed with a valid JSONPath expression (e.g. $.foo) because ClickHouse raises error code 36 (BADARGUMENTS)…

Published by the source

4 Jun 2026, 18:39 UTC

Last modified by the source

4 Jun 2026, 18:39 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wc3v-3457-c8cm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-8462

Advisory: OpenMeter: SQL injection through meter creation
IDs: CVE-2026-8462, GHSA-wc3v-3457-c8cm
Record: https://patchnext.com/advisories/cve-2026-8462 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openmeterio/openmeter 1.0.0-beta.228. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openmeterio/openmeter: affected < 1.0.0-beta.228; fixed in 1.0.0-beta.228

## Suggested inspection (read-only)
- Go github.com/openmeterio/openmeter: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openmeterio/openmeter.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wc3v-3457-c8cm (GitHub-reviewed advisory GHSA-wc3v-3457-c8cm lists affected ranges: Go github.com/openmeterio/openmeter >=0 <1.0.0-beta.228)

Commands are suggestions: review each one before running it.