<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Heartex - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/heartex/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 24 Aug 2026 20:06:10 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/heartex/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>IDOR Vulnerability in Label Studio Annotation API</title><link>https://feed.craftedsignal.io/briefs/2026-08-label-studio-idor/</link><pubDate>Mon, 24 Aug 2026 20:06:10 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-label-studio-idor/</guid><description>Label Studio contains an insecure direct object reference (IDOR) vulnerability, CVE-2026-76073, allowing authenticated users to read, modify, or delete annotations across organizational boundaries by enumerating sequential identifiers.</description><content:encoded><![CDATA[<p>Label Studio, a popular open-source data labeling tool maintained by Heartex, contains a critical insecure direct object reference (IDOR) vulnerability identified as CVE-2026-76073. The flaw exists within the 'AnnotationAPI' and 'AnnotationConvertAPI' endpoints defined in 'label_studio/tasks/api.py'. The application fails to properly scope querysets to the requesting user's organization. While other endpoints, such as the task-specific API, correctly constrain data access by checking 'project__organization', the annotation endpoints default to 'Annotation.objects.all()'. Because these endpoints only verify basic authentication rather than enforcing object-level authorization, any logged-in user can access any annotation in the system. Furthermore, since annotation identifiers are assigned as sequential integers, an attacker can trivially enumerate these IDs to exfiltrate or manipulate sensitive annotation data belonging to other organizations hosted on the same instance. This vulnerability poses a significant risk to the confidentiality and integrity of proprietary datasets within multi-tenant Label Studio environments.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows any authenticated user to gain unauthorized access to annotation data across organizational silos. Impact includes the potential for full data exfiltration of labels, the modification of labeling tasks which could poison machine learning pipelines, and the deletion of project work. This is particularly critical in multi-tenant environments where organizations expect strict data isolation.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Upgrade Label Studio to a patched version once provided by Heartex to remediate CVE-2026-76073.</li>
<li>Implement an application-layer firewall or web application firewall (WAF) to monitor for anomalous spikes in API requests targeting the annotation endpoints (e.g., sequentially incrementing IDs).</li>
<li>Audit webserver access logs for high-volume HTTP GET, PATCH, and DELETE requests to '/api/annotations/' from low-privileged user accounts.</li>
<li>Ensure that all organizational members are vetted and that the instance is restricted to trusted users until the patch is applied.</li>
</ol>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>idor</category><category>api-security</category><category>data-exfiltration</category></item></channel></rss>