# CVE-2026-38568: Missing authorization in n/a

> Authenticated users can access any candidate profile or interview note by manipulating URL IDs, leading to unauthorized data disclosure and horizontal privilege escalation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-6fpq-hhv8-hc9f

## What is CVE-2026-38568?

CVE-2026-38568 is a high-severity missing authorization vulnerability in n/a, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HireFlow v1.2 is vulnerable to Incorrect Access Control. The application does not enforce object-level authorization on the /candidate/<id> and /interview/<id> endpoints. The route handlers retrieve records by the user-supplied ID without verifying that the requesting user is the owner or has an authorized role. Any authenticated user can access any other user's candidate profiles and interview notes by iterating the integer ID in the URL path, constituting a horizontal privilege escalation and full data breach of all records in the system.

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

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


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

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

## Is CVE-2026-38568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38568 is a high-severity missing authorization vulnerability in n/a, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38568 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-38568/ (Markdown: https://insights.sbomify.com/CVE-2026-38568/index.md)
```

## Sources

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

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