# CVE-2026-16216: geex-arts django-jet OAuth cross-site request forgery

> Attackers can perform cross-site request forgery against the OAuth handler in the django-jet library, potentially bypassing security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 19 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-48hv-4375-2378

## What is CVE-2026-16216?

CVE-2026-16216 is a medium-severity vulnerability in geex-arts django-jet, published on 19 Jul 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

A weakness has been identified in geex-arts django-jet up to 1.0.8. Affected is an unknown function of the component OAuth Handler. Executing a manipulation can lead to cross-site request forgery. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-16216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16216 is a medium-severity vulnerability in geex-arts django-jet, published on 19 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16216 exists.

Affected product: geex-arts django-jet. 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-16216/ (Markdown: https://insights.sbomify.com/CVE-2026-16216/index.md)
```

## Sources

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

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