Security readout for executives and security teams
Plain-English summary
DIGIKENT has an access-control weakness that can expose sensitive system information to unauthorised parties. The published CVSS score is 8.2 because the issue is network-reachable, requires no login, and can seriously affect confidentiality. Public sources do not name a patch or confirm exploitation.
Executive priority
Prioritise this for any organisation using DIGIKENT because unauthenticated remote exposure of sensitive system information can support follow-on compromise. Urgency is high, but evidence is incomplete on exploitation and fixes.
Technical view
CVE-2025-9986 is mapped to CWE-497: exposure of sensitive system information. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, indicating unauthenticated remote exposure with high confidentiality impact and low integrity impact. The record says DIGIKENT is affected through 13092025, but version metadata is sparse.
Likely exposure
Exposure is likely limited to organisations running Vadi Corporate Information Systems DIGIKENT through 13092025, especially network-accessible deployments. The CVE record does not provide CPEs or detailed deployment context, so asset inventory is required.
Exploitation context
No cited source or KEV entry confirms active exploitation. The CVSS vector suggests exploitation would not require authentication or user interaction, but the public bundle does not provide exploit details, proof-of-concept status, or observed attacks.
Researcher notes
The record contains limited technical detail. One referenced USOM link is tagged broken in the bundle, and affected-version metadata appears thin. Do not assume exploitability beyond the CVSS vector and official description without vendor advisory confirmation.
Mitigation direction
- Check Vadi and Turkish government advisories for corrected versions or official mitigations.
- Inventory DIGIKENT deployments and identify versions through 13092025.
- Restrict untrusted network access to DIGIKENT until vendor guidance is applied.
- Review exposure of sensitive system information and rotate secrets if confirmed exposed.
Validation and detection
- Confirm whether any owned systems run Vadi DIGIKENT through 13092025.
- Review perimeter records for externally reachable DIGIKENT services.
- Check vendor and government advisories for patch, configuration, or lifecycle guidance.
- Search logs for unauthorised access to system-information endpoints or administrative data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-497: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-9986 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2TR-CERTVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.usom.gov.tr/bildirim/tr-26-0056CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0056CVE reference, TR-CERT · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.