CVE-2026-1495
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 · uneditedThe vulnerability, if exploited, could allow an attacker with Event Log Reader (S-1-5-32-573) privileges to obtain proxy details, including URL and proxy credentials, from the PI to CONNECT event log files. This could enable unauthorized access to the proxy server.
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 confidenceThe vulnerability allows users with Event Log Reader privileges (S-1-5-32-573) to access proxy configuration details, including URLs and credentials, stored within or associated with PI to CONNECT event log files. This information disclosure occurs due to insufficient access controls on sensitive proxy configuration data that gets written to or accessible through the event log system.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Verify PI to CONNECT installationCheck if PI to CONNECT or related OSIsoft/AVEVA PI software is installed on the system by reviewing installed programs in Control Panel > Programs and Features, or running: Get-WmiObject -Class Win32_Product | Select-Object Name, VersionAffected if PI to CONNECT software is present on the system
-
Identify Event Log Reader group membersCheck which users or groups belong to the Event Log Readers built-in group (S-1-5-32-573) by running: Get-LocalGroupMember -Group 'Event Log Readers' or using ADSI if domain-managedAffected if Any non-administrative users or groups are members of the Event Log Readers group
-
Search event logs for proxy configuration entriesOpen Windows Event Viewer and search all event logs (Application, System, Operational logs) for entries containing keywords such as 'proxy', 'credential', 'username', 'password', 'authentication', or URL patterns (http://, https://) that may indicate proxy configuration dataAffected if Event log entries containing proxy URLs, credentials, or authentication details are visible in readable logs
-
Inspect PI to CONNECT event log files directlyLocate and examine PI to CONNECT-specific event log files or ETW traces stored in the PI installation directory (typically under \pidata or \logs) and check for unencrypted proxy configuration data within those filesAffected if PI to CONNECT event log files contain plaintext proxy URLs or credentials accessible to Event Log Readers
If PI to CONNECT is installed and event logs or log files contain accessible proxy configuration data (URLs or credentials) that can be read by Event Log Reader members, the environment is affected by this vulnerability.
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 dataRestrict Event Log Reader membership to only essential personnel and investigate where proxy credentials are being stored in event log contexts. Implement proper encryption and access controls on proxy configuration data to prevent unauthorized reads by low-privileged users.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1495 — 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-1495 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