CVE-2025-62646VulnerabilityPublished 17 Oct 2025Updated 29 Oct 2025

CVE-2025-62646: Restaurant Brands International assistant platform · Incorrect Resource Transfer Between Spheres

Affects Restaurant Brands International assistant platformSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Restaurant Brands International assistant platform	Affected =0	Fixed in–

AI-suggested

1. Implement strict role-based access controls (RBAC) to ensure that only authorized personnel can access stored audio recordings. 2. Conduct a thorough audit of current access permissions within the RBI assistant platform to identify and revoke unnecessary privileges. 3. Employ network segmentation to isolate the assistant platform and its storage systems from broader corporate networks, reducing the attack surface. 4. Monitor and log all access to audio storage resources, setting up alerts for anomalous or unauthorized access attempts. 5. Enforce multi-factor authentication (MFA) for all users with privileges that could access sensitive audio data. 6. Engage with RBI or platform vendors to obtain patches or security updates as soon as they become available. 7. If patches are not yet available, consider deploying compensating controls such as temporary disabling of remote access to audio storage or encrypting stored audio files at rest with strict key management. 8. Provide training and awareness to staff about the risks of credential compromise and insider threats. 9. Regularly review and update incident response plans to include scenarios involving unauthorized access to customer audio data. 10. Ensure compliance with GDPR and other relevant privacy regulations by documenting data handling and breach response procedures related to this vulnerability.

Description

The Restaurant Brands International (RBI) assistant platform through 2025-09-06 allows remote attackers to review the stored audio of conversations between associates and Drive Thru customers.

Impact

For European organizations using the RBI assistant platform, this vulnerability poses a significant confidentiality risk. The unauthorized access to stored audio conversations can lead to exposure of personally identifiable information (PII) of customers and associates, potentially violating GDPR and other privacy regulations. This can result in legal penalties, regulatory scrutiny, and financial losses. Additionally, the leakage of customer interaction data can damage brand reputation and customer trust, especially in the competitive food service industry. Since the vulnerability requires some level of privilege but no user interaction, insider threats or compromised credentials could be leveraged to exploit this flaw remotely. The impact is particularly critical for franchises and operations in Europe where RBI brands have a strong presence, as these organizations handle large volumes of customer data daily. Furthermore, the scope change in the vulnerability means that attackers could access data beyond their initial access level, increasing the potential damage. Although availability and integrity are not affected, the confidentiality breach alone warrants urgent attention.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 15:37 UTC

WeaknessesCWE-669

Technical details

References

Community reviews

Related threats