CVE-2026-39558
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 · uneditedUnauthenticated Local File Inclusion in Malmö <= 2.2 versions.
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 · moderate confidenceAn unauthenticated Local File Inclusion vulnerability in Malmö version 2.2 and earlier allows remote attackers to read sensitive files on the server by manipulating file path parameters without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Malmö web application is installedCheck for Malmö web application files in the web server document root or application directory. Common paths include /var/www/html/malmo, /opt/malmo, or check your package manager for malmo packages.Affected if The Malmö web application is present on the server
-
Determine installed Malmö versionLocate the version file or check the application header/footer for a version number. Common locations: version.php, VERSION file, or the main index.php file often contains a version constant.Affected if Installed version is 2.2 or below, or if the version cannot be determined (assumed vulnerable)
-
Identify if file inclusion functionality is enabledSearch the application source code for file inclusion functions (include, require, include_once, require_once, fread with file paths) that process user-supplied input without validation. Check routing configuration for endpoints that accept file path parameters.Affected if File inclusion functionality that accepts user input exists and is accessible without authentication
-
Verify directory traversal is possible in file inclusion parametersTest suspected file inclusion endpoints with directory traversal sequences such as ../../../../etc/passwd or ../../../../windows/win.ini to see if arbitrary file contents are returned.Affected if The application returns contents of files outside the intended directory when traversal sequences are provided
If Malmö web application version 2.2 or below is running and the file inclusion functionality is accessible without authentication, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Malmö to a version newer than 2.2; if no patch is available, implement WAF rules to block path traversal patterns and apply strict input validation on file inclusion functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39558 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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