CVE-2026-111364 mindoc-org CVE debrief

Who should care

Defenders responsible for MinDoc instances, especially those with multiple users or sensitive documents, should assess exposure and prioritize remediation. This includes reviewing instance configurations, verifying document access controls, and ensuring that users with non-observer roles cannot access unauthorized documents. Security teams should also monitor for suspicious activity and review logs to detect potential exploitation attempts.

Why it matters

CVE-2026-111364 is a high-severity IDOR vulnerability in MinDoc through 2.2-beta.2, allowing authenticated users to read documents from unauthorized books. Defenders should prioritize verifying exposure and remediating vulnerable instances to prevent potential data exposure.

• Authenticated users can read documents from unauthorized books
• Potential data exposure for sensitive documents
• Requires verification of MinDoc instance exposure and document access controls

Technical summary

The vulnerability exists in the DocumentController.Content API endpoint of MinDoc through 2.2-beta.2, allowing authenticated users to read documents from unauthorized books by iterating sequential document IDs. This insecure direct object reference (IDOR) vulnerability enables attackers to access sensitive information from private books without proper authorization. The affected endpoint allows users to retrieve document content using a GET request with the book key and document ID as parameters. Defenders should prioritize verifying exposure and remediating vulnerable MinDoc instances, especially in environments with multiple users or sensitive documents.

Defensive priority

Defenders should prioritize verifying exposure and remediating vulnerable MinDoc instances, especially in environments with multiple users or sensitive documents.

Recommended defensive actions

• Verify MinDoc instance exposure and document access controls
• Remediate vulnerable MinDoc instances to version 2.2-beta.3 or later
• Monitor document access and authentication logs for suspicious 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 source item provide details on the vulnerability, including its impact and affected versions. However, additional information on exploitation or victim organizations is not available.

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.