Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
ExploitObtain or enumerate victim's chatid
-
ExecutionSubmit chatid to /aibot2 endpoint
-
ImpactRead, exfiltrate, or delete victim's AI conversation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated low-privilege account on the target REBUILD instance (through 4.5.0) with the AiBot2 assistant feature in use. The attacker must supply another user's chatid to the /aibot2 chat-init, chat-delete, chat-feedback, or chat-stream-stop endpoints, which act on the caller-supplied chatid without verifying ownership. The key limiting factor is obtaining a valid victim chatid - reflected in AC:H - so predictability or enumerability of chatids directly governs exploitability; exploitation is constrained to authenticated users and has no effect on single-user or non-multi-tenant deployments. No user interaction by the victim is required. |
| Impact | This is a moderate-severity authorization bypass (IDOR, CWE-639) whose real-world urgency is tempered by its access requirements. The CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:L/UI:N) confirms network reachability but requires an authenticated low-privilege account (PR:L) and carries high attack complexity (AC:H), reflecting the need to obtain or enumerate another user's chatid rather than exploit a default/predictable value. Impact is skewed toward confidentiality (VC:H - reading/exfiltrating other users' AI conversations) with only limited integrity impact (VI:L - deleting or interrupting conversations) and no availability or scope impact. Exploitation status: no public exploit identified at time of analysis, though a detailed technical write-up (hackmd) with direct vulnerable source-code references exists and materially lowers the barrier to developing one. EPSS is not provided in the input, so exploitation probability cannot be quantified. KEV status is NO - no confirmed active exploitation. On balance this is a legitimate but not emergency-tier issue: it affects authenticated users only, impacts a niche open-source product, and lacks evidence of weaponization. It merits prompt patching for exposed multi-tenant REBUILD deployments but does not rank with unauthenticated RCE or KEV-listed flaws. |
| Exploit ScenarioDerived | A low-privilege but authenticated user of a shared REBUILD instance obtains or enumerates another user's chatid and submits it to an /aibot2 endpoint (e.g. chat-init or chat-stream-stop) to read, exfiltrate, delete, or interrupt that victim's AI assistant conversation. No public exploit code is identified, but a published technical write-up pinpoints the vulnerable controller and ChatManager code paths, making exploitation straightforward for anyone with an account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
REBUILD through 4.5.0 provides an authorization bypass (IDOR, CWE-639) in its AiBot2 AI-assistant endpoints, letting an authenticated low-privilege user act on another user's chat by supplying that user's chatid to chat-init, chat-delete, chat-feedback, or chat-stream-stop. Successful exploitation allows reading and exfiltrating conversation content (high confidentiality impact), deleting chats, and interrupting active streams, with limited integrity impact and no direct availability loss to the application as a whole. The attack is network-reachable but rated AC:H because the attacker must first obtain or guess a valid victim chatid, and it only matters on multi-user deployments where the AiBot2 assistant feature is in use; no KEV entry or public exploit code was identified at time of analysis, and EPSS data was not provided.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation must currently be compensatory. If AiBot2 is not essential, disable the AI-assistant module or block the /aibot2 endpoints (in particular chat-init, chat-delete, chat-feedback, and chat-stream-stop) at the reverse proxy or web application firewall - the trade-off is loss of the assistant feature. If the feature must stay enabled, restrict access to a small trusted group via an authorization filter or IP allowlist and enforce server-side ownership checks as a code-level fix, ensuring every chat operation validates that the chatid belongs to the authenticated principal before acting. Because the attack hinges on obtaining a valid chatid, reduce exposure by making chat identifiers long, random, and non-sequential, avoiding them in URLs, logs, and client-side telemetry, and monitoring AiBot2 logs for a single account touching multiple chatids or chat operations that do not correspond to its own sessions; rotate or re-key existing chats if chatid leakage is suspected. Also review the referenced source at the getrebuild commit and the VulnCheck advisory (https://www.vulncheck.com/advisories/rebuild-through-4.5.0-authorization-bypass-via-aibot2-chat-endpoints-chatid) plus the researcher write-up (https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/getrebuild-rebuild-aibot-chat-idor) for updated fix guidance before relying on version upgrades alone.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-639 authorization bypass through a user-controlled key, implemented in the Java/Spring codebase of REBUILD (com.rebuild.web.aibot.AiBot2Controller, with chat handling in com.rebuild.core.aibot2.ChatManager). The controller endpoints referenced in the source links (AiBot2Controller.java lines ~151-203 and ChatManager.java lines ~99-101) accept a caller-supplied chatid parameter and operate on the corresponding chat record without first confirming that the requesting principal owns or is authorized for that chat. Because chat identifiers are the sole access key and are not scoped to the session user, any authenticated account that can reach the /aibot2 surface can pivot into other users' AI conversations. The CPE cpe:2.3:a:getrebuild:rebuild:*:*:*:*:*:*:*:* indicates the advisory treats all versions as potentially affected up to and including 4.5.0, and the associated CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N) confirms the high confidentiality exposure alongside low integrity impact: reads and exports are the primary payoff, deletions and stream interruptions are secondary, and no victim interaction is required. The High attack-complexity rating reflects that success hinges on obtaining a valid chatid - so any predictability, enumeration, logging, or leakage of chatids materially raises real-world exploitability.
Know when Rebuild gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Authenticated low-privilege web access (PR:L) plus the need to obtain a victim chatid (AC:H); reading others' conversations gives C:H, deletion/interruption gives I:L, no availability or scope impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
REBUILD through 4.5.0 contains an authorization bypass vulnerability in AiBot2Controller /aibot2 endpoints that act on a caller-supplied chatid without verifying ownership. Authenticated low-privilege users can supply another user's chatid to chat-init, chat-delete, chat-feedback, or chat-stream-stop to read, delete, exfiltrate, or interrupt AI assistant conversations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
A vulnerability, which was classified as critical, has been found in Rebuild up to 3.5.5. Rated critical severity (CVSS
A vulnerability, which was classified as critical, was found in Rebuild up to 3.2.3. Rated critical severity (CVSS 9.8),
A vulnerability, which was classified as critical, has been found in Rebuild up to 3.2.3. Rated critical severity (CVSS
A vulnerability classified as critical was found in Rebuild up to 3.2.3. Rated high severity (CVSS 8.8), this vulnerabil
A vulnerability was found in Rebuild up to 3.5.5 and classified as problematic.getStorageFile of the file /filex/proxy-d
A Server-Side Request Forgery (SSRF) in Rebuild v2.8.3 allows attackers to obtain the real IP address and scan Intranet
A vulnerability classified as problematic was found in Rebuild up to 3.5.5. Rated medium severity (CVSS 6.1), this vulne
Rebuild instances up to and including 4.4.7 and 4.5.0-beta5 expose a login endpoint (/user/login) that fails to properly
Missing authorization in REBUILD up to 4.4.11 allows unauthenticated remote attackers to manipulate the url or fileKey p
A vulnerability was found in Rebuild up to 3.5.5. Rated medium severity (CVSS 5.4), this vulnerability is remotely explo
A vulnerability, which was classified as problematic, was found in ruifang-tech Rebuild 3.8.5. Rated medium severity (CV
A vulnerability, which was classified as problematic, has been found in ruifang-tech Rebuild 3.8.5. Rated medium severit
EUVD-2026-101239
GHSA-c434-7979-wrg6
NVD
CVE.org
EPSS
Exploit-DB