# CVE-2026-30233: OliveTin: View permission not being checked when returning dashboards

> Authenticated users with view permissions disabled can enumerate action metadata and titles due to missing authorization checks in dashboard endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** Yes
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-jf73-858c-54pg, GO-2026-4629

## What is CVE-2026-30233?

CVE-2026-30233 is a medium-severity missing authorization vulnerability in OliveTin, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OliveTin gives access to predefined shell commands from a web interface. Prior to version 3000.11.1, an authorization flaw in OliveTin allows authenticated users with view: false permission to enumerate action bindings and metadata via dashboard and API endpoints. Although execution (exec) may be correctly denied, the backend does not enforce IsAllowedView() when constructing dashboard and action binding responses. As a result, restricted users can retrieve action titles, IDs, icons, and argument metadata. This issue has been patched in version 3000.11.1.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including github.com/OliveTin/OliveTin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260305082002-d7962710e7c4 |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260305082002-d7962710e7c4 |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260305082002-d7962710e7c4 |

Products: Olivetin Olivetin.

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

Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260305082002-d7962710e7c4 or later.

## Is CVE-2026-30233 being exploited?

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

## Other vulnerabilities in OliveTin

- [CVE-2026-27626](https://insights.sbomify.com/CVE-2026-27626/): OliveTin: OS Command Injection via `password` argument type and webhook JSON extraction bypasses shell safety checks (critical 10.0)
- [CVE-2026-30223](https://insights.sbomify.com/CVE-2026-30223/): OliveTin: JWT Audience Validation Bypass in Local Key and HMAC Modes (high 8.8)
- [CVE-2026-31817](https://insights.sbomify.com/CVE-2026-31817/): OliveTin's unsafe parsing of UniqueTrackingId can be used to write files (high 8.5)
- [CVE-2026-28342](https://insights.sbomify.com/CVE-2026-28342/): OliveTin: Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint (high 7.5)
- [CVE-2026-28789](https://insights.sbomify.com/CVE-2026-28789/): OliveTin: Unauthenticated DoS via concurrent map writes in OAuth2 state handling (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30233 is a medium-severity missing authorization vulnerability in OliveTin, published on 6 Mar 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-30233 exists.

Affected packages and fixed versions:
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260305082002-d7962710e7c4
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260305082002-d7962710e7c4
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260305082002-d7962710e7c4

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

## Sources

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

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