OVERVIEW CVE-2026-35548 is a logic flaw in guardsix (formerly Logpoint) ODBC Enrichment Plugins versions before 5.2.1 that affects guardsix 7.9.0.0 and earlier. The vulnerability allows stored database credentials to be inappropriately reused when an administrator modifies connection parameters such as the target host, IP address, or port on an existing enrichment source. An authenticated operator could exploit this flaw to redirect database connections to unintended internal systems while reusing valid credentials. SEVERITY The vulnerability carries a CVSS 3.1 score of 8.5 (HIGH) with a network-based attack vector requiring low complexity and authenticated access. The attack has a changed scope with high confidentiality impact and low integrity impact, indicating potential unauthorized data access and system manipulation. With an EPSS score of 0.00028, the probability of exploitation is currently low relative to other known vulnerabilities, though the moderate FAUCET risk score of 51.0 suggests moderate concern. EXPLOITATION STATUS There is no evidence of active exploitation, as the vulnerability does not appear on the Known Exploited Vulnerabilities (KEV) catalog and is currently inactive on threat intelligence hot lists. No publicly available exploit code has been reported. The low EPSS score and absence from active threat tracking suggest limited community attention and exploitation activity at this time. However, organizations running affected versions should prioritize patching to version 5.2.1 or later.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
< 7.9.0CPE matchmatch criteria | cpe:2.3:a:guardsix:logpoint:*:*:*:*:*:*:*:* | ||
< 5.2.1CPE matchmatch criteria | cpe:2.3:a:guardsix:odbc:*:*:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.3 Bluesky, 0.1 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.