CVE-2026-112045 donetick CVE debrief

Who should care

Defenders responsible for donetick deployments should assess exposure and verify proper authorization controls. Defenders should verify donetick versions up to 0.1.82 for exposure, assess the History Deletion Handler's configuration, and ensure proper authorization controls are in place. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

Defenders should verify donetick versions up to 0.1.82 for exposure and ensure proper authorization controls are in place to prevent improper authorization.

• Verify proper authorization controls for donetick History Deletion Handler
• Assess exposure of donetick versions up to 0.1.82
• Ensure configuration aligns with security best practices

Technical summary

The vulnerability affects donetick up to 0.1.82, specifically the CanDeleteHistory function in internal/chore/model/model.go. The issue allows remote attackers to manipulate the AssignedTo argument, leading to improper authorization. The project maintainer views this as a bug rather than a security vulnerability, given its limited impact to trusted circle members. Defenders should verify donetick versions up to 0.1.82 for exposure, assess the History Deletion Handler's configuration, and ensure proper authorization controls are in place.

Defensive priority

Defenders should verify donetick versions up to 0.1.82 for exposure, assess the History Deletion Handler's configuration, and ensure proper authorization controls are in place.

Recommended defensive actions

• Verify donetick versions up to 0.1.82 for exposure
• Assess the History Deletion Handler's configuration
• Ensure proper authorization controls are in place
• 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, including its description, CVSS score, and affected versions. However, the impact and remediation require further verification from official sources. Defenders should verify donetick versions up to 0.1.82 for exposure, assess the History Deletion Handler's configuration, and ensure proper authorization controls are in place. The project maintainer views this as a bug rather than a security vulnerability, given its limited impact to trusted circle members. Evidence is  

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.