CVE-2026-73219 cvat-ai CVE debrief

Who should care

Defenders managing CVAT deployments, especially those with multiple users having write access to jobs, should assess exposure and verify they are running the fixed version. Defenders should prioritize verifying exposure in CVAT deployments, especially those with multiple users having write access to jobs, and ensure they are running version 2.72.0 or later. Operators of CVAT should review user access controls and monitor for suspicious activity related to

Why it matters

CVE-2026-73219 is a MEDIUM-severity vulnerability in CVAT that allows a user to block automatic annotation for another task. Defenders should verify exposure, especially in deployments with multiple users having write access to jobs, and ensure they are running version 2.72.0 or later.

• Potential denial of service for automatic annotation
• Need to verify exposure in CVAT deployments
• Requires updating to version 2.72.0 or later
• Limited information on potential data impact

Technical summary

The vulnerability in CVAT allows a user with write access to a job to block automatic annotation for another task by submitting a request with inconsistent task and job IDs. This issue is fixed in version 2.72.0. The vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. A user with write access to a CVAT job can submit a batch automatic annotation request to RequestViewSet.create with inconsistent task and job IDs, and because the task ID determines the single active request slot, block automatic annotation for another task whose ID is known.

Defensive priority

Defenders should prioritize verifying exposure in CVAT deployments, especially those with multiple users having write access to jobs, and ensure they are running version 2.72.0 or later.

Recommended defensive actions

• Verify CVAT version and ensure it is 2.72.0 or later
• Review user access controls for CVAT jobs
• Monitor for suspicious activity related to automatic annotation requests
• 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 scope of affected deployments and potential impact require further verification.

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.