Advisory record · GHSA-h746-rm5q-8mgq

Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node

CVSS 8.1 HighEPSS 0.0056 · 47th percentile

Published by the GitHub Advisory Database at 21 May 2021, 14:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/spiffe/spireGo>=0.8.1, <0.8.5 || >=0.9.0, <0.9.4 || >=0.10.0, <0.10.2 || >=0.11.0, <0.11.3 || >=0.12.0, <0.12.10.8.5, 0.9.4, 0.10.2, 0.11.3, 0.12.1
Identifiers
GHSA-h746-rm5q-8mgq · CVE-2021-27098
Weakness (CWE)
CWE-284 · CWE-295
Published
21 May 2021
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Go module github.com/spiffe/spire, versions 0.8.1 through 0.8.4, 0.9.0 through 0.9.3, 0.10.0 through 0.10.1, 0.11.0 through 0.11.2, and 0.12.0, is affected. An attacker holding a valid agent certificate that is already authorized for at least one SPIFFE ID in the same trust domain can send crafted requests to the FetchX509SVID RPC of the Legacy Node API and obtain an X.509 certificate with a URI SAN for a SPIFFE ID the agent is not authorized to distribute. Upgrade to 0.8.5, 0.9.4, 0.10.2, 0.11.3, or 0.12.1, as applicable. No workarounds are identified.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.