# CVE-2026-35548: Server-side request forgery in n/a

> An authenticated operator can redirect database connections to internal systems by modifying endpoint details, leading to SSRF and credential misuse.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-j95x-gpg4-q4w9

## What is CVE-2026-35548?

CVE-2026-35548 is a high-severity server-side request forgery vulnerability in n/a, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-35548?

It affects 2 products.


Products: Guardsix Logpoint, Guardsix Odbc.

## How do I fix CVE-2026-35548?

No fix has been published for CVE-2026-35548 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35548 being exploited?

There is no known exploitation of CVE-2026-35548 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35548 and fix it if it is affected.

What it is: CVE-2026-35548 is a high-severity server-side request forgery vulnerability in n/a, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35548 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35548/ (Markdown: https://insights.sbomify.com/CVE-2026-35548/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35548
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35548
- OSV: https://osv.dev/vulnerability/CVE-2026-35548

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35548/
Summaries are generated and may contain mistakes; the official description above is the record.