# CVE-2026-67990: Cross-site request forgery in n/a

> An attacker can trick logged-in users into triggering unauthorized actions on upstream monitoring services via disabled CSRF protection in proxy controllers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-q9r6-h8cx-q7qp

## What is CVE-2026-67990?

CVE-2026-67990 is a medium-severity vulnerability in n/a, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

basecamp/upright at commit efe4f2e5254ac6e57e45d2261804cca74dbbca3f disables Rails CSRF protection for its Alertmanager and Prometheus proxy controllers. An unauthenticated attacker can induce a logged-in user's browser to submit requests that are forwarded to enabled upstream write or management endpoints, such as creating an Alertmanager silence or requesting a Prometheus reload. The final impact depends on the APIs enabled by the upstream services.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-67990 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67990 is a medium-severity vulnerability in n/a, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-67990 in the wild and no public exploit code.

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

## Sources

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

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