dbcve.org
LogpointApplication · Guardsix

CVE-2026-35548

HIGH · 8.5 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 5.2.1 / 7.9.0 or later.
See remediation →
91/100
Remediation priority · Urgent
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
An issue was discovered in guardsix (formerly Logpoint) ODBC Enrichment Plugins before 5.2.1 (5.2.1 is used in guardsix 7.9.0.0). A logic flaw allowed stored database credentials to be reused after modification of the target Host, IP address, or Port. When editing an existing Enrichment Source, previously stored credentials were retained even if the connection endpoint was changed. An authenticated Operator user could redirect the database connection to unintended internal systems, resulting in SSRF and potential misuse of valid stored credentials.

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 confidence

The ODBC Enrichment Plugins in guardsix (formerly Logpoint) contain a logic flaw where stored database credentials persist even when the connection endpoint (Host, IP, or Port) is modified. When an authenticated Operator edits an existing Enrichment Source and changes the connection target, previously stored credentials are retained without re-authentication, allowing redirection of database connections to unintended internal systems and enabling SSRF attacks.

MitigationUpgrade to guardsix version 7.9.0.0 (which includes ODBC Enrichment Plugins 5.2.1) to obtain the fix. Until patched, monitor Enrichment Source configurations for unauthorized endpoint changes and consider restricting Operator permissions to modify Enrichment Sources.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LogpointApplication
Affected:< 7.9.0
OdbcApplication
Affected:< 5.2.1

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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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. Check installed guardsix Logpoint version
    Run 'rpm -qi logpoint' or check the product version in the UI under Settings > About
    Affected if The version is below 7.9.0
  2. Check installed guardsix ODBC plugin version
    Run 'rpm -qi guardsix-odbc' or check the plugin version in the product interface
    Affected if The version is below 5.2.1
  3. Identify configured ODBC Enrichment Sources
    Navigate to Enrichment configuration or run 'lpcmd enrichment list' to view all Enrichment Sources with type ODBC
    Affected if ODBC Enrichment Sources are configured and actively used
  4. Review Enrichment Source endpoint configurations
    Compare current Host, IP, and Port values against known legitimate database endpoints. Check configuration files or export Enrichment settings to audit current values
    Affected if Any Enrichment Source endpoint differs from the originally documented or expected database endpoint
  5. Audit recent modification logs for Enrichment Sources
    Check Operator audit logs or system logs for events indicating Enrichment Source edits, specifically focusing on connection parameter changes (Host, IP, Port) by authenticated Operators
    Affected if Endpoint modifications were performed by Operators without documented approval

A user is affected if they are running guardsix Logpoint below version 7.9.0 or ODBC plugins below version 5.2.1 AND have ODBC Enrichment Sources configured where endpoint changes have occurred without credential re-authentication.

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
Upgrade available Upgrade to 5.2.1 / 7.9.0 or later
Fixed in 5.2.17.9.0
Interim mitigation

Upgrade to guardsix version 7.9.0.0 (which includes ODBC Enrichment Plugins 5.2.1) to obtain the fix. Until patched, monitor Enrichment Source configurations for unauthorized endpoint changes and consider restricting Operator permissions to modify Enrichment Sources.

Recommended fix High confidence

guardsix 7.9.0.0 (includes ODBC Enrichment Plugins 5.2.1)

  1. Upgrade Logpoint to version 7.9.0.0 or later, which includes the fixed ODBC Enrichment Plugins version 5.2.1
  2. If using standalone ODBC Enrichment Plugins, upgrade to version 5.2.1 or later
  3. After upgrade, verify that Enrichment Sources require re-entry of credentials when connection endpoints are modified
  4. Test that credential fields are properly cleared when editing existing Enrichment Sources in the UI

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

Fix this in Logpoint Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35548 — 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-35548 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