# CVE-2026-3999: Broken access control vulnerability affecting ID Server

> Authenticated users can perform horizontal privilege escalation in Pointsharp ID Server under specific configurations, allowing unauthorized access to other users' data.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA: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:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-2p4q-qchf-h9q6

## What is CVE-2026-3999?

CVE-2026-3999 is a high-severity authentication bypass vulnerability in Pointsharp ID Server, published on 13 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A broken access control may allow an authenticated user to perform a 
horizontal privilege escalation. The vulnerability only impacts specific
 configurations.

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

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

It affects 1 product.


Products: Pointsharp Id Server.

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

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

## Is CVE-2026-3999 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3999 is a high-severity authentication bypass vulnerability in Pointsharp ID Server, published on 13 Mar 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-3999 in the wild and no public exploit code.

Affected product: Pointsharp ID Server. 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-3999/ (Markdown: https://insights.sbomify.com/CVE-2026-3999/index.md)
```

## Sources

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

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