Unbounded memory usage on exposed HTTP/2 (non-gRPC) endpoints

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The net/http Go package has a reported vulnerability tracked under CVE-2021-44716 which allows attacker controlled HTTP/2 requests to trigger unbounded memory usage in HTTP/2 endpoints. gRPC endpoints are not vulnerable as they rely on their own HTTP/2 implementation instead of the net/http package. HTTP/2 endpoints consuming the net/http package within SPIRE server and agent (or other components in this repository) that are on by default include the following: - OIDC Discovery Provider - K8s Workload Registrar in webhook mode The following endpoints are vulnerable when enabled: - SPIRE server bundle endpoint (i.e. Federation API) The following endpoints are NOT vulnerable, since HTTP/2 support in go is not enabled on non-TLS protected endpoints: - SPIRE server/agent metrics endpoint when configured for Prometheus - SPIRE server/agent health endpoints - SPIRE server/agent profiling endpoints Patches SPIRE 1.0.3 and 1.1.3 have been released with an upgraded Go toolchain which…

Published by the source

12 Jan 2022, 22:33 UTC

Last modified by the source

11 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m7vp-hqwv-7m5x

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

# Patch Next advisory brief: GHSA-m7vp-hqwv-7m5x

Advisory: Unbounded memory usage on exposed HTTP/2 (non-gRPC) endpoints
IDs: GHSA-m7vp-hqwv-7m5x
Record: https://patchnext.com/advisories/ghsa-m7vp-hqwv-7m5x (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/spiffe/spire 1.1.3, 1.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/spiffe/spire: affected < 1.0.3; >= 1.1.0, < 1.1.3; fixed in 1.1.3, 1.0.3

## Suggested inspection (read-only)
- Go github.com/spiffe/spire: 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/spiffe/spire.
- 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-m7vp-hqwv-7m5x (GitHub-reviewed advisory GHSA-m7vp-hqwv-7m5x lists affected ranges: Go github.com/spiffe/spire >=0 =1.1.0 <1.1.3)

Commands are suggestions: review each one before running it.