CVE-2025-41359
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 · uneditedVulnerability related to an unquoted service path in Small HTTP Server 3.06.36, specifically affecting the executable located at 'C:\Program Files (x86)\shttps_mg\http.exe service'. This misconfiguration allows a local attacker to place a malicious executable with the same name in a higher priority directory, causing the service to execute the malicious file instead of the legitimate one. Exploiting this flaw could allow arbitrary code execution, unauthorized access to the system, or service disruption. To mitigate the risk, the service path must be properly quoted, and systems must be kept up to date with security patches, while restricting physical and network access.
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 confidenceThis is an unquoted service path vulnerability in Small HTTP Server 3.06.36. The service executable path 'C:\Program Files (x86)\shttps_mg\http.exe' contains spaces and is not enclosed in quotes, causing Windows to search for executables in intermediate directories before locating the intended binary. A local attacker can place a malicious 'http.exe' in a higher-priority directory to achieve arbitrary code execution with service privileges.
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.06.36, < 3.06.38CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Small HTTP Server service existsOpen Command Prompt as Administrator and run: sc query state= all | findstr /i "small http"Affected if No service matching Small HTTP Server is found (not vulnerable as service is not installed)
-
Check if service executable path is unquotedRun: sc qc "ServiceName" (replace with actual service name found in step 1). Look at the BINARY_PATH_NAME field - check if it contains spaces and lacks opening and closing quotes.Affected if BINARY_PATH_NAME contains spaces and does NOT start and end with double quotes (e.g., C:\Program Files (x86)\shttps_mg\http.exe without quotes)
-
Identify the service name and exact executable pathRun: wmic service where "name like '%small%' or name like '%http%'" get name,displayname,pathname,startname /format:listAffected if The pathname shows the vulnerable path C:\Program Files (x86)\shttps_mg\http.exe without quotes
-
Verify installed version is within affected rangeLocate the http.exe file in the installation directory (typically C:\Program Files (x86)\shttps_mg\). Right-click http.exe, select Properties, then查看 Version tab. Alternatively run: powershell (Get-Item 'C:\Program Files (x86)\shttps_mg\http.exe').VersionInfo.FileVersionAffected if File version is 3.06.36 or higher but lower than 3.06.38
-
Check for exploitable intermediate directoriesInspect the service path directories: verify if C:\Program.exe exists, or if C:\Program Files.exe exists, or if C:\Program Files (x86)\shttps_mg\ exists as separate directories. Run: dir C:\ | findstr /i "^.*\.exe$" and dir "C:\Program Files (x86)\shttps_mg" /bAffected if Any executable exists in an intermediate directory along the unquoted path (e.g., C:\Program.exe) that could be invoked by Windows service startup
A user is affected if the Small HTTP Server service is installed, the service binPath contains the unquoted path with spaces (C:\Program Files (x86)\shttps_mg\http.exe), and the version falls within 3.06.36 through 3.06.37, creating a condition where malicious executables in intermediate directories could be invoked with service privileges.
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.
dbcve · scoped3.06.38
Enclose the service executable path in quotes within the Windows service configuration (via sc command or registry) to prevent path traversal. Verify the service starts correctly after applying the fix.
3.06.38 or later
- Identify the currently installed version of Small HTTP Server by checking the service properties in Windows Services or the Add/Remove Programs list
- Download Small HTTP Server version 3.06.38 or later from the official vendor source
- Stop the Small HTTP Server service if it is currently running
- Install the updated version of Small HTTP Server
- Verify that the new version is installed by checking the service properties in Windows Services
- Confirm the service executable path is now properly quoted (e.g., "C:\Program Files (x86)\shttps_mg\http.exe")
- Restart the Small HTTP Server service
- Test that the server functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41359 — 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-41359 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