Security readout for executives and security teams
Plain-English summary
A logged-in attacker with a valid Pangolin access token for one protected resource may reuse it to reach other resources, including those belonging to different organizations. This breaks tenant and resource isolation and could expose or alter sensitive systems without affecting availability.
Executive priority
Treat this as an urgent isolation failure. Promptly identify affected Pangolin deployments, reduce access-token exposure, and follow confirmed vendor remediation. Prioritize multi-organization or internet-accessible environments because one legitimate token could undermine boundaries protecting unrelated resources.
Technical view
Pangolin through v1.20.0 reportedly fails to enforce the resource and organization scope of access tokens. The network-accessible authorization flaw requires low privileges, no user interaction, and has cross-scope confidentiality and integrity impact. It is classified as CWE-639 with CVSS 3.1 score 9.6.
Likely exposure
Potentially exposed environments are Pangolin deployments through v1.20.0 that use access-token authentication for multiple resources or organizations. Risk is greatest where users or integrations can obtain any valid token. The supplied affected-version metadata is inconsistent, listing version “0” while the description says through v1.20.0, so confirm applicability with vendor guidance.
Exploitation context
The supplied record describes remote exploitation by an authenticated attacker holding a valid access token. It does not establish public exploit availability or observed attacks, and the CVE is not listed as KEV in the bundle. Do not treat exploitation as active without additional evidence.
Researcher notes
The central issue is an authorization-object mismatch consistent with CWE-639: token validity may be checked without binding authorization to the requested resource and organization. The bundle identifies authWithAccessToken.ts as relevant, but provides no confirmed patch version, workaround, exploit evidence, or detailed affected-version range beyond the narrative claim.
Mitigation direction
- Inventory Pangolin deployments and identify instances running v1.20.0 or earlier.
- Check the Pangolin project and CVE record for confirmed remediation guidance.
- Restrict access-token use and externally reachable resources where operationally feasible.
- Review and revoke unnecessary access tokens as a precaution, without treating rotation as a complete fix.
Validation and detection
- Confirm deployed Pangolin versions and document all organizations and protected resources.
- Determine whether access-token authentication is enabled and who can obtain tokens.
- Review authentication logs for tokens accessing unexpected resources or organizations.
- Verify vendor remediation restores explicit resource and organization scope enforcement.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-72564 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
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:L/UI:N/S:C/C:H/I:H/A:N3.15.8TuranSecVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineTuranSec
CVE Reserved
- Source timelineTuranSec
Public Disclosure
- 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
- ProductCVE reference, TuranSec · third-party-advisory
- Vulnerable FileCVE reference, TuranSec · technical-description
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.