VulnerabilityPublished 9 Oct 2025

CVE-2025-61779: confidential-containers trustee · Insecure Direct Object Reference

Affects confidential-containers trusteeSource CVE Database V5

Not known to be exploited · CVSS 8.7 High : upgrade to 0.15.0 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

8.7High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.15.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 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 26 Oct 2026.

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

Upgrade confidential-containers trustee to 0.15.0.

Affected software

Product	Affected	Fixed in
confidential-containers trustee	Affected <0.15.0	Fixed in 0.15.0

AI-suggested

The primary mitigation is to upgrade the Confidential Containers Trustee project to version 0.15.0 or later, where the vulnerability is fixed by enforcing authentication on the attestation-policy endpoint. Organizations should audit their current attestation policies to detect any unauthorized changes that may have occurred prior to patching. Implement network segmentation and access controls to restrict which clients can communicate with the Trustee service, minimizing exposure. Employ strong authentication and authorization mechanisms for all components interacting with the Trustee, including kbs-clients. Monitor logs and alerts for unusual policy modification attempts or access patterns. Integrate vulnerability scanning and configuration management to ensure no outdated Trustee versions are deployed. Finally, educate DevOps and security teams about the importance of secure attestation policy management and the risks of this vulnerability to prevent future misconfigurations.

Description

CVE-2025-61779 is a high-severity authorization bypass vulnerability in the Confidential Containers Trustee project versions prior to 0.15.0. The flaw exists because the attestation-policy endpoint does not verify if the requesting kbs-client is authenticated or authorized, allowing any client to modify attestation policies. This can lead to unauthorized changes in security policies governing confidential guest attestation and secret provisioning. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Version 0.15.0 of the Trustee project addresses this issue by enforcing proper authentication checks. European organizations using Confidential Containers Trustee in affected versions are at risk of unauthorized policy manipulation, potentially compromising confidentiality and integrity of sensitive workloads.

Impact

For European organizations leveraging confidential computing and containerized workloads, this vulnerability poses a significant risk. Unauthorized modification of attestation policies can allow attackers to bypass security controls, potentially enabling untrusted or malicious workloads to access sensitive secrets or data. This compromises confidentiality and integrity, which are paramount in sectors such as finance, healthcare, and government. The ability to remotely exploit this vulnerability without authentication or user interaction increases the attack surface, especially in multi-tenant cloud environments common in Europe. Organizations relying on Confidential Containers Trustee for secure attestation and secret management may face data breaches, regulatory non-compliance (e.g., GDPR), and reputational damage. The vulnerability could also facilitate lateral movement within networks if attackers use compromised policies to escalate privileges or access additional resources. Given the growing adoption of confidential computing in Europe, the impact could be widespread if not promptly mitigated.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2025, 05:23 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats