# CVE-2026-123184: Incorrect Authorization in Altium 365 Git Service Allows Unauthorized Repository Writes


- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-2fff-cjw5-9mmr

## What is CVE-2026-123184?

CVE-2026-123184 is a high-severity vulnerability in Altium 365, published on 5 Nov 2026. 

### Official description

An incorrect authorization vulnerability exists in the Altium 365 Git Service. The permission check performed when a user pushes to a project repository did not correctly evaluate the required access level, so the check passed for any user holding any level of access to the project. As a result, an authenticated user with view-only access to a project could write to that project's git repository.

Read access was evaluated correctly and was not affected, and exploitation requires an authenticated account with existing access to the target project. The issue has been remediated in Altium 365 at the service level and no customer action is required. On-premise Altium Enterprise Server is not affected.

Weakness: CWE-863 (Incorrect Authorization), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-123184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123184 is a high-severity vulnerability in Altium 365, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123184 in the wild and no public exploit code.

Affected product: Altium 365. 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-123184/ (Markdown: https://insights.sbomify.com/CVE-2026-123184/index.md)
```

## Sources

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

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