Security readout for executives and security teams
Plain-English summary
Grafana Loki 2.3.0 has a path traversal issue that can let an unauthenticated remote attacker read files through the Ruler rules API. The reported impact is confidentiality only, with low data exposure severity. No source in the bundle reports active exploitation.
Executive priority
Treat as a targeted, moderate-priority confidentiality risk. It is not currently supported as actively exploited, but exposed Loki 2.3.0 services should be identified and remediated through Grafana guidance.
Technical view
This is a bypass of the CVE-2021-36156 fix. The namespace parameter is validated after one URL decode, but double encoding can bypass traversal filtering at /loki/api/v1/rules/{namespace}. CVSS 3.1 is 5.3: network-reachable, low complexity, no privileges, no user interaction, low confidentiality impact.
Likely exposure
Exposure is likely limited to Grafana Loki 2.3.0 deployments where the Ruler API endpoint is reachable by untrusted users or networks. The source bundle lists other versions as unaffected by default, but does not provide complete deployment context.
Exploitation context
The vulnerability is remotely reachable and unauthenticated according to the CVSS vector. KEV status is false, and the provided sources do not cite known active exploitation or public weaponization.
Researcher notes
The key issue is decode-order handling in namespace traversal validation. Evidence supports a double-encoding bypass against the Ruler API, but the bundle does not include exploit details, fixed versions, or indicators of compromise.
Mitigation direction
- Check Grafana's advisory for official remediation and fixed-version guidance.
- Inventory environments for Grafana Loki 2.3.0 specifically.
- Prioritize systems where the Ruler API is exposed to untrusted networks.
- Review access controls around Loki API endpoints during remediation planning.
- Do not assume CVE-2021-36156 mitigation fully covers Loki 2.3.0.
Validation and detection
- Confirm installed Loki versions across production and non-production environments.
- Identify whether /loki/api/v1/rules/{namespace} is reachable externally or by untrusted users.
- Review logs for unusual requests to the Ruler rules API endpoint.
- Map any exposed Loki 2.3.0 instances to owners and data sensitivity.
- Track remediation status against Grafana's published advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-21726 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4GRAFANAVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://grafana.com/security/security-advisories/cve-2026-21726CVE reference, GRAFANA · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.