Security readout for executives and security teams
Plain-English summary
An authenticated user could potentially access or alter another customer's administrative resources in Sage AR Automation by supplying that tenant's valid, hard-to-guess identifier. This creates serious cross-customer confidentiality, integrity, and availability risk. Exploitation requires an account and knowledge of another tenant identifier, but no user interaction.
Executive priority
Treat as an immediate remediation and investigation priority wherever June-R1-2026 is present. The vulnerability crosses customer boundaries and may affect sensitive administrative data or operations. Assign ownership now, confirm vendor remediation status, preserve relevant logs, and investigate unusual cross-tenant activity. Evidence does not currently show exploitation in the wild.
Technical view
CVE-2026-67403 is a CWE-639 improper authorization flaw affecting Sage AR Automation June-R1-2026. The API insufficiently enforces tenant-level authorization before returning administrative resources. CVSS 4.0 rates it 9.0: network-accessible, high complexity, low privileges, no user interaction, with high impacts to vulnerable and subsequent systems.
Likely exposure
Exposure is indicated for Sage AR Automation June-R1-2026. Risk primarily concerns authenticated API users who can obtain a valid tenant identifier belonging to another customer. The identifier is described as non-predictable, reducing opportunistic abuse, but the sources do not establish how identifiers might be disclosed or discovered.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. Abuse requires authentication, a valid cross-tenant identifier, and overcoming high attack complexity. Successful exploitation could permit unauthorized access to another tenant's administrative resources; the precise accessible operations and data are not documented here.
Researcher notes
The weakness maps to CWE-639 and appears to be object-level authorization failure at the tenant boundary. Assessment should focus on consistent server-side tenant ownership enforcement across administrative API resources. Public evidence does not identify specific endpoints, resource types, exploitation observations, or an explicit fixed version; avoid inferring these from the release-page title alone.
Mitigation direction
- Identify deployments or service instances running the affected June-R1-2026 release.
- Review Sage's June-R2 release guidance and confirm whether the vendor identifies it as the corrective release.
- Apply the vendor-supported update or mitigation after confirming its applicability and change requirements.
- Restrict API access and unnecessary user privileges while remediation status is being established.
- Escalate suspected cross-tenant access to Sage and activate incident-response procedures.
Validation and detection
- Confirm the deployed Sage AR Automation release through authoritative inventory or vendor records.
- Verify with Sage whether the affected service has received the relevant corrective update.
- Review API and administrative logs for accounts accessing resources associated with multiple tenants.
- Test tenant isolation only in an authorized non-production environment using controlled accounts and tenant data.
- After remediation, confirm cross-tenant administrative requests are denied and legitimate same-tenant operations still succeed.
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-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 lookupCVE-2026-67403 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 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
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:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——hackeroneVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
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://helpcenter.sara.sage.com/hc/en-us/articles/52106283946651-June-R2-Release-2026CVE reference, hackerone
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.