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

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Altium / Altium 365: Version not specified (affected). Source: CNA: Altium; platforms: Web

## Severity and prioritization

- CVSS 4.0: 7.2 (high); 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; source: CNA: Altium

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-863, CWE-20

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.altium.com/platform/security-compliance/security-advisories (CNA: Altium)

## Provenance

- CNA: Altium: https://www.cve.org/CVERecord?id=CVE-2026-123184; retrieved 2026-11-05; source updated 2026-11-05

Revision: 3b6f0d762313233078e666deff2bc5976563547ab9e4cf7ee3363f6dee7d54ff

Canonical: https://y2.dev/cve/CVE-2026-123184

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.