Skip to main content
VulnerabilityPublished Updated

CVE-2021-41803: HashiCorp Consul · Missing Authorization

Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in 1.11.9 : patch affected systems soon.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • >=1.8.1 <=1.11.8
  • =1.12.4
  • =1.13.1
Fixed in–

AI-suggested

European organizations should prioritize upgrading HashiCorp Consul to the fixed versions 1.11.9, 1.12.5, or 1.13.2 as soon as possible to remediate this vulnerability. Beyond patching, organizations should implement strict network segmentation and firewall rules to restrict access to Consul RPC endpoints, limiting exposure to trusted internal networks only. Employing mutual TLS authentication for Consul communication can further reduce the risk of unauthorized access. Monitoring and logging of Consul RPC calls should be enhanced to detect anomalous or malformed requests indicative of exploitation attempts. Organizations should also review and harden JWT claim validation logic in their Consul configurations and consider disabling auto config RPC if not required. Conducting regular security assessments and penetration testing focused on service mesh components can help identify similar weaknesses. Finally, incident response plans should include scenarios for service mesh disruptions to ensure rapid recovery and continuity.

Description

HashiCorp Consul 1.8.1 up to 1.11.8, 1.12.4, and 1.13.1 do not properly validate the node or segment names prior to interpolation and usage in JWT claim assertions with the auto config RPC. Fixed in 1.11.9, 1.12.5, and 1.13.2."

References

Community reviews

Loading reviews…