# CVE-2026-109568: Shaark 1.2.13 through 1.2.44 Missing Authorization via API Update and Delete Routes

> Authenticated users can modify or delete other users' content in Shaark due to missing ownership checks in API routes.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA: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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-33mg-5c73-726g

## What is CVE-2026-109568?

CVE-2026-109568 is a high-severity missing authorization vulnerability in MarceauKa Shaark, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Shaark 1.2.13 through 1.2.44 contains a missing authorization vulnerability in the Link, Story, Chest and Album API controllers that skips ownership checks. Authenticated non-admin users can send PUT or DELETE requests to /api/{link,story,chest,album}/{id} with numeric IDs to overwrite or delete other users' content, including private items.

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

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


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

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

## Is CVE-2026-109568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109568 is a high-severity missing authorization vulnerability in MarceauKa Shaark, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109568 in the wild and no public exploit code.

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

## Sources

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

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