# CVE-2026-130859: Habitat through 1.7.1 IDOR via Post Creation Attachment IDs


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-2955-456r-p77r

## What is CVE-2026-130859?

CVE-2026-130859 is a medium-severity vulnerability in carlnewton Habitat, published on 17 Nov 2026. 

### Official description

Habitat through 1.7.1 contains an insecure direct object reference vulnerability in CreatePostController::addAttachmentsToPost() that allows authenticated users to claim other users' unposted image uploads. Email-verified attackers can submit sequential attachmentIds when creating a post to attach another user's pending image, exposing it publicly and removing it from the uploader's post.

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

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

1 open source package ship an affected version, including carlnewton/habitat.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `carlnewton/habitat` | GitHub | `pkg:github/carlnewton/habitat` | All versions to 1.7.1 | None |

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

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

## Is CVE-2026-130859 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130859 is a medium-severity vulnerability in carlnewton Habitat, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130859 in the wild and no public exploit code.

Affected packages and fixed versions:
- carlnewton/habitat (GitHub): affected all versions up to 1.7.1; no fix listed

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

## Sources

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

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