CVE-2026-114374 leomoon-studios CVE debrief

Who should care

Defenders responsible for wiki-go deployments should assess exposure and prioritize upgrading to version 1.9.2. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and implement necessary mitigations. Defenders should also review compensating controls for exposed systems and monitor for potential server-side request forgery attacks.

Why it matters

Defenders should care about CVE-2026-114374 because it allows for server-side request forgery in wiki-go versions up to 1.9.1, potentially leading to unauthorized access, data breaches, and service disruption. Verification of exposure and upgrading to version 1.9.2 are crucial.

• Potential unauthorized access to internal resources
• Possible data breaches due to SSRF
• Required verification of wiki-go versions and patching
• Potential disruption of service due to exploitation

Technical summary

A vulnerability in leomoon-studios wiki-go up to 1.9.1 allows for server-side request forgery due to improper handling of the fetch-metadata endpoint in internal/handlers/metadata_api.go. This could lead to unauthorized access, data breaches, and service disruption. Defenders should prioritize verifying exposure and upgrading to version 1.9.2. The CVE record and source item provide details on the vulnerability, affected versions, and patch information. The exploit is publicly available, and defenders should review the official CVE Program record and NIST NVD detail page for additional information.

Defensive priority

Defenders should prioritize verifying exposure of wiki-go versions up to 1.9.1 and upgrading to version 1.9.2.

Recommended defensive actions

• Verify exposure of wiki-go versions up to 1.9.1
• Upgrade to version 1.9.2
• Monitor for potential server-side request forgery attacks
• 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 source item provide details on the vulnerability, affected versions, and patch information. Defenders should verify exposure by checking wiki-go versions up to 1.9.1 and review the official CVE Program record and NIST NVD detail page for additional information. The exploit is publicly available, and upgrading to version 1.9.2 is recommended. Evidence limits suggest that further verification is required to confirm affected scope and severity.

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.