CVE-2026-114375 leomoon-studios CVE debrief

Who should care

Defenders responsible for wiki-go installations, particularly those using versions up to 1.9.1, should assess exposure and prioritize mitigation. This includes reviewing current version deployments, verifying exposure, and planning for upgrades or patch applications. Security teams and vulnerability management teams should also be aware of the potential impacts and prioritize mitigation efforts.

Why it matters

CVE-2026-114375 is a path traversal vulnerability in wiki-go up to 1.9.1 that allows remote attackers to manipulate file paths. Defenders should prioritize upgrading to version 1.9.2 or applying the patch. Evidence is limited, so verification of exposure and impacts is necessary.

• Potential unauthorized file access or modification
• Need for verification of current version and exposure
• Priority for upgrading to version 1.9.2 or applying the patch
• Limited information on potential exploits or impacts requires cautious assessment

Technical summary

The RenameFileHandler function in internal/handlers/files.go of wiki-go up to 1.9.1 is vulnerable to path traversal attacks. This allows remote attackers to manipulate file paths, potentially leading to unauthorized file access or modification. The issue is addressed in version 1.9.2 and through patch 81cd12e248314a52605f0f39718c8a76272eac29. The vulnerability is caused by insufficient input validation, allowing attackers to traverse the file system. Defenders should prioritize upgrading to version 1.9.2 or applying the patch to mitigate this vulnerability.

Defensive priority

Defenders should prioritize upgrading to version 1.9.2 or applying the patch (81cd12e248314a52605f0f39718c8a76272eac29) to mitigate this vulnerability.

Recommended defensive actions

• Upgrade wiki-go to version 1.9.2 or later
• Apply the patch (81cd12e248314a52605f0f39718c8a76272eac29) to affected versions
• Review and update inventory of wiki-go installations to ensure version 1.9.2 or later is deployed
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details about the vulnerability, including its existence in versions up to 1.9.1 and a fix in version 1.9.2. However, there is limited information on potential exploits or impacts.

Sources and 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.