# CVE-2026-6355: CVE-2026-6355

> Unauthorized users can access and modify sensitive tenant data via insecure direct object references in the Augmentt web application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-mhrx-6c4m-w27r

## What is CVE-2026-6355?

CVE-2026-6355 is a medium-severity missing authorization vulnerability in Augmentt, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web application allows unauthorized users to access and manipulate sensitive data across different tenants by exploiting insecure direct object references. This could lead to unauthorized access to sensitive information and unauthorized changes to the tenant's configuration.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Augmentt Augmentt.

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

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

## Is CVE-2026-6355 being exploited?

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

Public exploit code:

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

## Other vulnerabilities in Augmentt

- [CVE-2026-6356](https://insights.sbomify.com/CVE-2026-6356/): CVE-2026-6356 (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6355 is a medium-severity missing authorization vulnerability in Augmentt, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6355 in the wild and no public exploit code.

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

## Sources

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

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