PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-50138 patrickhener CVE debrief

CVE-2026-50138 debrief: goshs SimpleHTTPServer has a WebDAV mode-restriction bypass vulnerability. When launched with WebDAV enabled, the server does not enforce mode-restriction flags on the WebDAV port, allowing authenticated clients to perform unauthorized actions such as PUT, DELETE, MKCOL, MOVE, and COPY. Operators should assess exposure and verify configuration to prevent unauthorized actions. The vulnerability is patched in version 2.1.0, which enforces restrictions on both HTTP and WebDAV ports.

Vendor
patrickhener
Product
goshs
CVSS
HIGH 8.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-18
Original CVE updated
2026-09-18
Advisory published
2026-08-18
Advisory updated
2026-09-18

Who should care

Operators of goshs SimpleHTTPServer with WebDAV enabled should assess exposure and verify configuration to prevent unauthorized actions. This includes reviewing WebDAV settings, restricting access to trusted clients, and monitoring for suspicious activity. Security teams should prioritize patching to version 2.1.0 or later and ensure that compensating controls are in place for exposed systems.

Why it matters

CVE-2026-50138 allows authenticated WebDAV clients to perform unauthorized actions despite operator-configured restrictions. Operators should verify WebDAV configuration, restrict access, and monitor activity.

  • Verify WebDAV configuration to prevent unauthorized actions
  • Restrict access to trusted clients to prevent exploitation
  • Monitor for suspicious WebDAV activity to detect potential attacks

Technical summary

goshs SimpleHTTPServer, when launched with WebDAV enabled, does not enforce mode-restriction flags on the WebDAV port. This allows authenticated clients to perform unauthorized actions such as PUT, DELETE, MKCOL, MOVE, and COPY. The vulnerability is addressed in version 2.1.0, which ensures that restrictions are enforced on both the HTTP and WebDAV ports. Operators should verify WebDAV configuration and restrict access to trusted clients to prevent exploitation. The issue highlights the importance of securing WebDAV configurations and monitoring for suspicious activity.

Defensive priority

Operators should verify WebDAV configuration and restrict access to trusted clients

Recommended defensive actions

  • Verify WebDAV configuration and restrict access to trusted clients
  • Upgrade to version 2.1.0 or later
  • Monitor for suspicious WebDAV activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Additional information from the vendor and other sources is limited. The vulnerability allows authenticated WebDAV clients to perform unauthorized actions despite operator-configured restrictions. The issue is specific to the WebDAV port and does not affect the primary HTTP port. The patch in version 2.1.0 addresses this limitation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-50138 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-50138

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-50138 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-50138

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.