CVE-2026-0936
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 · uneditedAn Insertion of Sensitive Information into Log File vulnerability in B&R PVI client versions prior to 6.5 may be abused by an authenticated local attacker to gather credential information which is processed by the PVI client application. The logging function of the PVI client application is disabled by default and must be explicitly enabled by the user.
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 · high confidenceThe B&R PVI client versions prior to 6.5 contain a logging function that writes credential information to log files when explicitly enabled by the user. An authenticated local attacker with access to the system could read these log files to harvest sensitive credential data processed by the PVI client application.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PVI client installation and versionLocate the B&R PVI client installation directory and check for version information in the application metadata, README, or about dialog. Common locations may include Program Files\BR PVI or similar. Look for version files or executable properties.Affected if The installed version is prior to version 6.5
-
Determine if application logging is enabledCheck the PVI client configuration files or settings interface for logging-related options. Look for settings named 'logging', 'log enable', 'trace', or similar that control whether the application writes log files.Affected if Logging is explicitly enabled by the user in the PVI client configuration
-
Locate log file directoriesSearch for log directories or files associated with the PVI client installation. Common log locations may be within the application directory, a dedicated logs folder, or in system-wide application data locations.Affected if Log files or log directories exist for the PVI client
-
Inspect log file contents for credential exposureOpen any existing log files using a text editor and search for patterns that may indicate stored credentials, passwords, authentication tokens, or sensitive connection parameters.Affected if Log files contain credential data, passwords, or authentication tokens in plaintext
A user is affected if they have PVI client version prior to 6.5 with logging enabled and log files containing credential information are accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataEnsure the PVI client logging function remains disabled in production environments. If logging is required, restrict file system permissions on log directories to prevent unauthorized access, and upgrade to PVI client version 6.5 or later which addresses this vulnerability.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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