Incorrect Authorization in Altium 365 Git Service Allows Unauthorized Repository Writes
Affects the Altium 365 Git Service; on-premise Altium Enterprise Server is not affected.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects the Altium 365 Git Service; on-premise Altium Enterprise Server is not affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Altium 365's Git Service has an incorrect authorization flaw that lets a logged-in user with view-only access to a project write to that project's git repository. The attack can be launched remotely over the network, but it requires an authenticated account with existing access to the target project.
Read the original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects the Altium 365 Git Service; on-premise Altium Enterprise Server is not affected.Workaround: The available facts do not list a workaround or a fixed version. Check the vendor's advisory for any interim mitigation or fix status.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Altium Altium 365
Version range not reported
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123184
Is CVE-2026-123184 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw is an incorrect authorization check in the Altium 365 Git Service, which allows unauthorized parties to write to repositories. The available facts do not describe the exact mechanism.Source: altium.com
Am I affected, and how do I check?
The affected product is the Altium 365 Git Service. The facts list no specific version ranges. On-premise Altium Enterprise Server is stated not to be affected, so check whether your setup uses the Altium 365 Git Service or an on-premise Enterprise Server.Source: altium.com
What if there's no patch?
The available facts do not list a workaround or a fixed version. Check the vendor's advisory for any interim mitigation or fix status.Source: altium.com