dbcve.org
Small Http ServerWeb server / proxy · Smallsrv

CVE-2025-41368

HIGH · 8.1 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 3.06.38 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Problem in the Small HTTP Server v3.06.36 service. An authenticated path traversal vulnerability in '/' allows remote users to bypass the intended restrictions of SecurityManager and display any file if they have the appropriate permissions outside the document root configured on the server.

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

Small HTTP Server v3.06.36 contains an authenticated path traversal vulnerability in the root path '/' that allows authenticated users to bypass SecurityManager restrictions and access files outside the configured document root. The CVSS 8.1 score indicates high impact with network-exploitable authentication requirements.

MitigationApply vendor patch or update to a fixed version of Small HTTP Server; if unavailable, restrict authenticated user permissions and implement additional file system access controls at the operating system level to prevent unauthorized file access.

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
Small Http ServerWeb server / proxy
Affected:>= 3.06.36, < 3.06.38

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Small HTTP Server version
    Check the running service or executable properties: right-click on smallsrv.exe or the service, select Properties, then Details to view File Version; or run 'sc query' and 'sc qc smallsrv' if installed as a Windows service
    Affected if The version shown is 3.06.36 or 3.06.37 (versions 3.06.38 and later are fixed)
  2. Confirm authentication is enabled
    Inspect the server configuration file (typically httpd.conf or similar) for user authentication settings, looking for directives that enable login or user validation
    Affected if Authentication is enabled and user credentials are configured (the vulnerability requires valid authenticated access)
  3. Check SecurityManager configuration
    Look for SecurityManager or access control directives in the server configuration that restrict file access to within the document root
    Affected if SecurityManager restrictions are defined to limit file access (the vulnerability specifically bypasses these restrictions)
  4. Verify document root path setting
    Locate the document root or root path configuration directive in the server config to confirm a specific directory is set as the web root
    Affected if A document root is explicitly configured (the flaw allows traversing outside this directory)

You are affected if Small HTTP Server version is 3.06.36 or 3.06.37, authentication is enabled, and SecurityManager is configured to restrict file access to the document root.

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

Apply vendor patch or update to a fixed version of Small HTTP Server; if unavailable, restrict authenticated user permissions and implement additional file system access controls at the operating system level to prevent unauthorized file access.

Recommended fix High confidence

Small HTTP Server version 3.06.38 or latest stable release

  1. 1. Identify the current version of Small HTTP Server running in your environment.
  2. 2. If the version is >= 3.06.36 and < 3.06.38, plan for an upgrade to version 3.06.38 or later.
  3. 3. Download the updated Small HTTP Server version 3.06.38 or the latest stable release from the vendor.
  4. 4. Before upgrading, backup the current server configuration and data.
  5. 5. Apply the upgrade following the vendor's standard upgrade procedure.
  6. 6. Verify the server is running the updated version.
  7. 7. Test that the path traversal vulnerability is remediated by attempting to access files outside the document root with an authenticated account (ensure this is done in a test environment with authorization).

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

Fix this in Small Http Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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