# CVE-2026-130863: ArtisanCloud PowerX through 1.0.2 Privilege Escalation via IAM Role Endpoints


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-v2v9-5q73-m36f

## What is CVE-2026-130863?

CVE-2026-130863 is a high-severity vulnerability in ArtisanCloud PowerX, published on 17 Nov 2026. 

### Official description

ArtisanCloud PowerX through 1.0.2 contains a missing authorization vulnerability in the IAM role management API that allows authenticated tenant members to escalate privileges. Attackers holding even the lowest built-in role can call the permissions/grant-ids, permissions/grant, or bind/member routes to grant permissions or bind privileged roles, gaining tenant administrative access.

Weakness: CWE-862 (Missing Authorization)

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

1 open source package ship an affected version, including artisancloud/powerx.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `artisancloud/powerx` | GitHub | `pkg:github/artisancloud/powerx` | All versions to 1.0.2 | None |

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

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

## Is CVE-2026-130863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130863 is a high-severity vulnerability in ArtisanCloud PowerX, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130863 in the wild and no public exploit code.

Affected packages and fixed versions:
- artisancloud/powerx (GitHub): affected all versions up to 1.0.2; no fix listed

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-130863/ (Markdown: https://insights.sbomify.com/CVE-2026-130863/index.md)
```

## Sources

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

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