Case · DiggingBeagle record

OpenAI host-compromise tests found approved service paths could relay forbidden outbound requests

In a red-team exercise that assumed full host compromise, OpenAI found indirect paths from allowed monitoring, identity or DNS services to prohibited external destinations. The finding tests perimeter transit, not an actual production breach.

Scope

Controlled infrastructure egress testing after a hypothesized host compromise, not routine isolated training execution.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
Remediation
mitigation available
AI role
WITH AI
Basis and provenance

OpenAI described exploratory egress experiments under an assumed compromised-host starting condition. Service-mediated fetch paths were identified, but the report does not establish a real hostile host takeover or general bypass of every monitoring layer. Impact band is left null: observed consequences and counterfactual harm do not establish a justified numerical severity score.

Assessed Oct 25, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 23, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-OPENAI-EGRESS-ASSUMED-HOSTThe OpenAI egress study began with an assumed already-compromised host and identified indirect internet fetches through permitted metrics, authentication, DNS or error-processing intermediaries.supported

Basis: reported finding

Link to claim
CLM-OPENAI-TRANSITIVE-EGRESS-BYPASS-1OpenAI describes exercising outbound communication paths to metrics, authentication and DNS-related services while assuming an already compromised host.supported

Basis: reported finding

Link to claim
CLM-OPENAI-TRANSITIVE-EGRESS-BYPASS-2The authors found indirect external fetch or relay behaviors in allowed services but do not report confirmed unrelated production exfiltration.supported

Basis: reported finding

Link to claim

Unknowns and contradictions

  • Complete host/service denominator, final undetectable pathways and long-term effectiveness of mitigations are not public.

Sources and citation

Material revision history

  1. Oct 25, 2026 · Canonical change recorded · new in release · revision 191