CVE-2025-27906
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 · uneditedIBM Content Navigator 3.0.11, 3.0.15, 3.1.0, and 3.2.0 could expose the directory listing of the application upon using an application URL. Application files and folders are visible in the browser to a user; however, the contents of the files cannot be read obtained or modified.
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 confidenceIBM Content Navigator versions 3.0.11 through 3.2.0 contain a directory listing vulnerability where specific application URLs expose the file and folder structure of the application directory to users through the web browser. While the vulnerability allows viewing the directory contents, the description explicitly states that file contents cannot be read, obtained, or modified.
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= 3.0.11= 3.0.15= 3.1.0= 3.2.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM Content Navigator is installedInspect the web application server (IBM WebSphere or equivalent) for IBM Content Navigator web applications. Look for EAR/WAR files or application installations named 'Content Navigator' or similar. Check the web server's deployed applications list.Affected if IBM Content Navigator web application is deployed on the server
-
Determine the installed version of IBM Content NavigatorLocate the version information from the installed Content Navigator application. This may be found in version.properties files, the admin console, or by accessing the /api/version endpoint if available. Compare the installed version against the affected range: 3.0.11, 3.0.15, 3.1.0, or 3.2.0.Affected if The installed version matches 3.0.11, 3.0.15, 3.1.0, or 3.2.0
-
Verify if directory listing is accessibleAttempt to access known directory paths under the Content Navigator application URL, such as accessing the base application URL without an index file, or known subdirectories. Check if the browser returns a directory listing (showing file and folder names) rather than an access denied or default index page.Affected if Directory contents are displayed in the browser without requiring authentication or showing a default index file
You are affected if IBM Content Navigator versions 3.0.11, 3.0.15, 3.1.0, or 3.2.0 are installed AND directory listing is enabled on the web server, allowing unauthenticated users to view the application's directory structure through the browser.
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 dataConfigure the underlying web application server (IBM WebSphere or equivalent) to disable directory listing/browsing by setting appropriate access controls, removing directory index permissions, or ensuring default index files are served for all directories.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27906 — 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-2025-27906 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