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

> Attackers can trick authenticated users into performing unauthorized actions like password changes or data deletion due to missing CSRF protections.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-2qgc-8m4g-h724

## What is CVE-2026-38566?

CVE-2026-38566 is a high-severity vulnerability in n/a, published on 11 May 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

HireFlow v1.2 does not implement CSRF token validation on any state-changing POST endpoint. All forms (password change at /profile, candidate deletion at /candidates/delete/<id>, feedback submission at /feedback/add/<id>, interview scheduling at /interviews/add) are vulnerable to CSRF. An attacker who can trick an authenticated user into visiting a malicious page can silently change the victim's password, delete records, or inject arbitrary data on their behalf. The SESSION_COOKIE_SAMESITE attribute is also not configured, removing the browser-level CSRF defense.

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

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


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

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

## Is CVE-2026-38566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38566 is a high-severity vulnerability in n/a, published on 11 May 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-38566 exists.

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

## Sources

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

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