dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-7382

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor, Exposure of private personal information to an unauthorized actor vulnerability in MeWare Software Development Inc. PDKS allows Excavation. This issue affects PDKS: from V16.20200313 before VMYR_3.5.2025117.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

MeWare PDKS software versions from V16.20200313 before VMYR_3.5.2025117 contains an information disclosure vulnerability allowing unauthorized actors to access private personal information. This appears to be a broken access control or inadequate authentication mechanism enabling excavation of sensitive data.

MitigationUpdate PDKS to version VMYR_3.5.2025117 or later. Conduct a data access audit to determine what personal information may have been exposed and notify affected parties per data breach requirements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MeWare PDKS installation
    Locate the PDKS software installation directory or check installed programs list for 'MeWare PDKS' or related product names
    Affected if The software is installed on the system
  2. Determine installed PDKS version
    Check the software's version information, typically found in the application itself (about dialog), installation directory, or system registry under the PDKS program entry
    Affected if The version is V16.20200313 or any version from V16.20200313 up to but not including VMYR_3.5.2025117
  3. Verify network exposure
    Determine if the PDKS web interface or API is accessible from outside the local network by reviewing firewall rules, port bindings, or network configuration
    Affected if The software is exposed to untrusted networks without proper network segmentation
  4. Review access controls
    Check user authentication settings, role permissions, and any API endpoints that handle personal information within the PDKS configuration
    Affected if Anonymous or unauthenticated access is possible to data endpoints, or if weak authentication is configured
  5. Audit data access logs
    Review PDKS application logs for unexpected queries or access patterns to personal information tables, especially from unusual IP addresses or user accounts
    Affected if There are log entries showing unauthorized access to sensitive data tables

A user is affected if MeWare PDKS software is installed with a version between V16.20200313 and VMYR_3.5.2025117 (exclusive), particularly if the software is network-accessible or has weak access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update PDKS to version VMYR_3.5.2025117 or later. Conduct a data access audit to determine what personal information may have been exposed and notify affected parties per data breach requirements.

Recommended fix High confidence

VMYR_3.5.2025117 or later

  1. 1. Identify the current installed version of MeWare PDKS software.
  2. 2. If the current version is V16.20200313 or later but before VMYR_3.5.2025117, the system is vulnerable.
  3. 3. Contact MeWare Software Development Inc. to obtain the updated version VMYR_3.5.2025117 or later.
  4. 4. Before upgrading, perform a complete backup of the PDKS database and configuration files.
  5. 5. Test the upgrade in a non-production environment to verify compatibility with existing systems.
  6. 6. Apply the upgrade VMYR_3.5.2025117 or latest available version following vendor installation instructions.
  7. 7. Verify the fix by checking that the information exposure vulnerability is resolved.
  8. 8. After upgrade, review user access controls and audit logs to ensure no unauthorized access occurred during the vulnerability window.
Caveat Review vendor release notes for any configuration or behavioral changes in the new version; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7382 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data