# CVE-2026-76876: Craftplan < 0.5.1 Broken Access Control Information Disclosure via Settings API

> Unauthenticated attackers can read sensitive SMTP and email API credentials via the Settings API due to missing authorization checks.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-q329-hwc8-2x8j

## What is CVE-2026-76876?

CVE-2026-76876 is a high-severity missing authorization vulnerability in puemos craftplan, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Craftplan before 0.5.1 contains a broken access control vulnerability that allows unauthenticated attackers to read sensitive credentials by exploiting an unconditional authorization policy on the Settings resource. Attackers can send a GET request to the settings API endpoint with a valid record ID to retrieve decrypted SMTP passwords, email API keys, and email API secrets due to the read policy using an always-allow authorization check that bypasses all identity verification.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76876 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76876 is a high-severity missing authorization vulnerability in puemos craftplan, published on 21 Aug 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-76876 in the wild and no public exploit code.

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

## Sources

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

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