CVE-2026-50885: Sismics Docs v1.11 Unauthorized Access via Improper Share Endpoint Controls
Sismics Docs (also known as Teedy) version 1.11 contains a flaw in how it controls who can access certain file-sharing endpoints. An attacker without any credentials can craft a specially formed request to read sensitive information from the system. This is a remote attack that requires no special privileges or user interaction, making it relatively straightforward to exploit over the network.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-284
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Incorrect access control in the share-based read endpoints of Sismics Docs (Teedy) v1.11 allow unauthorized attackers to access sensitive endpoints via a crafted request.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-50885 is an improper access control vulnerability (CWE-284) in Sismics Docs v1.11 affecting the share-based read endpoints. The vulnerability allows unauthenticated attackers to bypass authorization checks and access restricted endpoints via a crafted HTTP request. The attack surface is network-accessible, requires no privileges or user interaction, and results in confidentiality impact through unauthorized information disclosure. The CVSS v3.1 score of 7.5 (HIGH) reflects the combination of remote exploitability, lack of authentication barriers, and high confidentiality impact.
Business impact
Unauthorized access to shared documents and metadata can lead to exposure of confidential business information, intellectual property, client data, or other sensitive materials stored within Sismics Docs. If your organization uses Teedy for document management with restricted sharing controls, this vulnerability could undermine those protections entirely. The lack of a required fix in KEV as of publication suggests this may not yet be weaponized at scale, but remediation should be prioritized nonetheless given the ease of exploitation.
Affected systems
Sismics Docs (Teedy) version 1.11 is confirmed affected. Users of earlier or later versions should consult the vendor's advisory to determine their exposure. The vulnerability does not require any specific configuration or feature enablement—it affects the core share-based read functionality. Any instance with network exposure is at risk.
Exploitability
This vulnerability has a low barrier to exploitation. No authentication is required, no special complexity is involved in crafting the malicious request, and the attack is triggered over standard network protocols. An attacker needs only network-level access to the affected endpoint. The lack of exploitation barriers and the simplicity of the attack vector mean that weaponized proof-of-concept code, once available, would be straightforward to deploy at scale.
Remediation
Upgrade Sismics Docs to a patched version released by the vendor after the vulnerability publication date (June 15, 2026). Consult the official Sismics or Teedy project repository for the specific patch version addressing CVE-2026-50885. If immediate patching is not possible, restrict network access to Docs instances using firewall rules or require a VPN gateway to limit exposure until a patch can be applied.
Patch guidance
Check the official Sismics Docs (Teedy) GitHub repository or project website for releases published after June 15, 2026 that explicitly reference CVE-2026-50885. Apply the recommended patch version to all affected instances. Test the patch in a non-production environment first to ensure compatibility with your document workflows and any custom integrations. After patching, verify that the share-based endpoints enforce proper access controls by testing with and without valid credentials.
Detection guidance
Monitor for HTTP requests to the share-based read endpoints (typically paths containing '/share/' or similar) that originate from sources without valid session tokens or API authentication. Log and alert on any 200 OK responses to these endpoints when authentication is expected. Review access logs for patterns of repeated requests to shared document endpoints by the same source or unusual geographic origins. Consider implementing intrusion detection signatures that identify crafted requests bypassing the normal share-access workflow.
Why prioritize this
Although not yet listed in CISA's KEV catalog, the HIGH CVSS score (7.5) combined with unauthenticated remote exploitability and high confidentiality impact makes this a priority-one remediation. Organizations using Sismics Docs for sensitive document storage should treat this as critical. The ease of exploitation and lack of user interaction required mean that delay increases the window of risk, especially if public exploit code emerges.
Risk score, explained
The CVSS v3.1 score of 7.5 reflects: (1) Network-accessible attack vector with no authentication required (AV:N, PR:N); (2) Low attack complexity—standard HTTP requests suffice (AC:L); (3) No user interaction needed (UI:N); (4) Unauthorized confidentiality impact through information disclosure (C:H); (5) No integrity or availability impact (I:N, A:N). The score appropriately captures a high-risk but non-critical vulnerability.
Frequently asked questions
Does this vulnerability affect all versions of Sismics Docs?
No. The vulnerability is confirmed in version 1.11. Earlier and later versions may or may not be affected. Consult the vendor's advisory or release notes to determine the full range of affected versions. Do not assume newer versions are automatically patched without verification.
Can this be exploited without network access to the Docs instance?
No. The attack requires network-level connectivity to the affected endpoint. Organizations that restrict access via firewall rules, VPN, or IP whitelisting reduce their exposure. However, if your Docs instance is exposed to the internet or accessible from untrusted networks, remediation is urgent.
Is there a workaround if we cannot patch immediately?
While a patch is strongly recommended, you can reduce risk by restricting network access to your Sismics Docs instance through firewall rules, requiring VPN authentication before allowing access, or temporarily disabling share-based endpoints if they are not critical to your operations. These are temporary mitigations only; patching is the proper fix.
What should we look for in logs to detect exploitation attempts?
Look for HTTP requests to share-based read endpoints that lack proper authentication headers or valid session cookies. Requests originating from external IP addresses accessing these endpoints, repeated failed or successful reads to multiple documents in a short timeframe, or unusual User-Agent strings can all signal reconnaissance or exploitation activity.
This analysis is provided for informational purposes to assist security professionals in understanding and addressing CVE-2026-50885. The vulnerability details and CVSS score are accurate as of the source data provided. Specific patch versions, vendor release notes, and advisory details should be verified directly with the Sismics Docs or Teedy project maintainers. SEC.co does not provide legal advice; organizations should consult their own risk management and compliance teams when determining remediation timelines. Unauthorized access to computer systems remains illegal; this information is intended only for defensive security purposes. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-22426HIGHAndroid ComputerEngine URI Escalation Privilege Vulnerability
- CVE-2025-46315HIGHmacOS Tahoe Permissions Flaw Enables Unauthorized Data Access
- CVE-2026-11179HIGHChrome ORB Site Isolation Bypass (CVSS 8.8)
- CVE-2026-11344HIGHUnrestricted File Upload in code-projects Vehicle Management System 1.0
- CVE-2026-11474HIGHUnrestricted File Upload in Kushan2k Student Management System
- CVE-2026-32995HIGHRocket.Chat DDP Authentication Bypass Exposes All Private Messages
- CVE-2026-35262HIGHOracle Data Integrator Authentication Bypass – Data Exposure Risk
- CVE-2026-35269HIGHOracle Identity Manager REST WebServices Authentication Bypass