# CVE-2026-6356: CVE-2026-6356

> Standard users can escalate privileges to super administrator via parameter manipulation, allowing access to and modification of sensitive information.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **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:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-pmj4-wrc3-26hm

## What is CVE-2026-6356?

CVE-2026-6356 is a critical vulnerability in Augmentt, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web application allows standard users to escalate their privileges to those of a super administrator through parameter manipulation, enabling them to access and modify sensitive information.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

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

It affects 1 product.


Products: Augmentt Augmentt.

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

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

## Is CVE-2026-6356 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6356 exists.

Public exploit code:

- Exploit PoC of CVE-2026-6356 (github_poc): https://github.com/Penguinsecq/CVE-2026-6356

## Other vulnerabilities in Augmentt

- [CVE-2026-6355](https://insights.sbomify.com/CVE-2026-6355/): CVE-2026-6355 (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6356 is a critical vulnerability in Augmentt, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6356 exists.

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

## Sources

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

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