CVE-2026-18744
CVE-2026-18744
Description
Any authenticated case participant can fetch any OTHER vendor's CaseStatement + per-vul CaseMemberStatus by supplying that member's id — test_func only checks _is_my_case, not ownership of kwargs['member']. Bypasses share_status; leaks embargoed vendor affected/not-affected + statement text cross-tenant.
INFO
Published Date :
Aug. 12, 2026, 10:17 p.m.
Last Modified :
Aug. 12, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-18744
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Validate case and member ownership before data access.
- Implement granular authorization controls for case data.
- Review and restrict cross-tenant data sharing.
- Apply vendor-specific security patches.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-18744.
| URL | Resource |
|---|---|
| https://github.com/CERTCC/VINCE | |
| https://github.com/CERTCC/VINCE/pull/235 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-18744 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-18744
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-18744 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-18744 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 12, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'CERT/CC', 'product': 'VINCE', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '3.0.44', 'versionType': 'custom'}]}] Added Description Any authenticated case participant can fetch any OTHER vendor's CaseStatement + per-vul CaseMemberStatus by supplying that member's id — test_func only checks _is_my_case, not ownership of kwargs['member']. Bypasses share_status; leaks embargoed vendor affected/not-affected + statement text cross-tenant. Added Reference https://github.com/CERTCC/VINCE Added Reference https://github.com/CERTCC/VINCE/pull/235