dbcve.org
KnowageApplication · Eng

CVE-2025-58441

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 8.1.37 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Knowage is an open source analytics and business intelligence suite. Prior to version 8.1.37, there is a blind server-side request forgery vulnerability. The vulnerability allows attackers to send requests to arbitrary hosts/paths. Since the attacker is not able to read the response, the impact of this vulnerability is limited. However, an attacker should be able to leverage this vulnerability to scan the internal network. This issue has been patched in version 8.1.37.

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

Blind server-side request forgery (SSRF) in Knowage analytics suite prior to version 8.1.37 allows attackers to send requests to arbitrary hosts and paths. While the attacker cannot read the response (blind SSRF), the vulnerability enables internal network scanning and potentially triggering further attacks against internal services.

MitigationUpgrade to Knowage version 8.1.37 or later to patch the SSRF vulnerability. Additionally, network segmentation and firewall rules can limit what hosts the application can reach.

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
KnowageApplication
Affected:< 8.1.37

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed Knowage version
    Access the Knowage administration interface and navigate to the 'About' or 'System Info' section to view the running version. Alternatively, check the installation directory for a VERSION file or examine startup logs for version information.
    Affected if The displayed version number is lower than 8.1.37 (for example, 8.1.36, 8.1.35, or earlier)
  2. Verify version via configuration file
    Locate the Knowage configuration file (commonly 'knowage.properties' or 'system.properties' in the installation conf directory) and search for a version parameter or metadata entry.
    Affected if The version entry in the configuration file shows a version below 8.1.37
  3. Determine application exposure
    Check whether the Knowage web interface is directly accessible from untrusted networks or the internet rather than being restricted to a trusted internal network via firewall or VPN.
    Affected if The application is exposed to the internet or untrusted users without network-level restrictions
  4. Check for SSRF-vulnerable endpoints
    Review the Knowage web application's URL parameters or API endpoints that accept user-supplied URLs, particularly in features related to external data sources, webhooks, or report exports.
    Affected if The application accepts arbitrary URLs from users in parameters such as 'url', 'endpoint', or 'redirect' without server-side validation

You are affected if your installed Knowage version is lower than 8.1.37 and the application is accessible to untrusted users or accepts external URL input.

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 8.1.37 or later
Fixed in 8.1.37
Interim mitigation

Upgrade to Knowage version 8.1.37 or later to patch the SSRF vulnerability. Additionally, network segmentation and firewall rules can limit what hosts the application can reach.

Recommended fix High confidence

8.1.37

  1. Back up the existing Knowage installation and its database before proceeding with the upgrade
  2. Download Knowage version 8.1.37 from the official GitHub releases repository (github.com) or official distribution channels
  3. Review the official Knowage upgrade/migration documentation for version 8.1.37
  4. Stop the Knowage application server
  5. Apply the upgrade by following the documented upgrade procedure (typically involves replacing application files and running any migration scripts)
  6. Start the Knowage application server
  7. Verify the installation by logging into Knowage and confirming core functionality works
  8. Confirm the version number displays as 8.1.37 in the About section or admin panel

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

Fix this in Knowage Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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