# CVE-2026-67403: Missing authorization in Sage AR Automation

> Authenticated users can access other tenants' administrative resources by guessing tenant identifiers, requiring immediate patching for Sage AR Automation.

- **Severity:** Critical 9.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-xwrh-qw65-q9mr

## What is CVE-2026-67403?

CVE-2026-67403 is a critical missing authorization vulnerability in Sage AR Automation, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cash Collect contains an improper authorization vulnerability in the Sage AR Automation API. Insufficient tenant-level authorization checks allow authenticated users to access administrative resources belonging to other tenants by specifying a valid non predictable tenant identifier.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-67403?


## How do I fix CVE-2026-67403?

No fix has been published for CVE-2026-67403 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67403 being exploited?

There is no known exploitation of CVE-2026-67403 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67403 and fix it if it is affected.

What it is: CVE-2026-67403 is a critical missing authorization vulnerability in Sage AR Automation, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67403 in the wild and no public exploit code.

Affected product: Sage AR Automation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67403/ (Markdown: https://insights.sbomify.com/CVE-2026-67403/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67403
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67403
- OSV: https://osv.dev/vulnerability/CVE-2026-67403

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67403/
Summaries are generated and may contain mistakes; the official description above is the record.