# CVE-2026-115657: KNIME Analytics Platform logs credentials of configured proxy when used as an executor


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-hgpp-4x3f-rrvq

## What is CVE-2026-115657?

CVE-2026-115657 is a medium-severity vulnerability in KNIME Analytics Platform, published on 23 Oct 2026. 

### Official description

When used as an executor in either KNIME Server or KNIME Business Hub, KNIME Analytics Platform LTS versions before 5.8.4 log configured credentials of proxies during startup. An attacker with access to log files can steal the credentials and use the proxy as the user who configured the proxy settings. The issue has been fixed in LTS versions 5.8.4 and 5.12.0 and later.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-115657 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115657 is a medium-severity vulnerability in KNIME Analytics Platform, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115657 in the wild and no public exploit code.

Affected product: KNIME Analytics Platform. 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-115657/ (Markdown: https://insights.sbomify.com/CVE-2026-115657/index.md)
```

## Sources

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

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