# CVE-2025-9986: Improper Access Control in Vadi Corporate Information System's DIGIKENT

> Attackers can access sensitive system information in DIGIKENT due to improper access controls, potentially exposing critical data.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-mw6j-4x6g-77v3

## What is CVE-2025-9986?

CVE-2025-9986 is a high-severity vulnerability in Vadi Corporate Information Systems Ltd. Co. DIGIKENT, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Vadi Corporate Information Systems Ltd. Co. DIGIKENT allows Excavation.

This issue affects DIGIKENT: through 13092025.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2025-9986?


## How do I fix CVE-2025-9986?

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

## Is CVE-2025-9986 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9986 and fix it if it is affected.

What it is: CVE-2025-9986 is a high-severity vulnerability in Vadi Corporate Information Systems Ltd. Co. DIGIKENT, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9986 in the wild and no public exploit code.

Affected product: Vadi Corporate Information Systems Ltd. Co. DIGIKENT. 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-2025-9986/ (Markdown: https://insights.sbomify.com/CVE-2025-9986/index.md)
```

## Sources

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

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