Technology / WORLD

AWS reports intended-path success on 33 of 37 fresh vulnerability tests

AWS published an evaluation on October 15 testing its security agent, now part of AWS Continuum, on 37 disclosed vulnerabilities from 2025–2026. It captured 35 flags in isolated, containerized targets; the company’s per-sample trajectory audit confirmed that 33 were obtained through the intended vulnerability. The adjusted success rate was 89.2%.

The source does not state the event date; the period shown is the source review period.

Reading sizeSources ↓Share story ↗
Conceptual illustration of technology, processors and connected information.Illustration
Symbolic illustration

AWS published an evaluation on October 15 testing its security agent, now part of AWS Continuum, on 37 disclosed vulnerabilities from 2025–2026. It captured 35 flags in isolated, containerized targets; the company’s per-sample trajectory audit confirmed that 33 were obtained through the intended vulnerability. The adjusted success rate was 89.2%. The run used Claude Opus 5 for one epoch with a 10-hour limit per sample.

Two captures used a different path and were counted as unsolved; in two other tests the target failed before the flag could be read. Runtime CVE and public exploit lookup was disabled. AWS describes the benchmark as contamination-reduced, without guaranteeing it is contamination-free; these are company-reported results for this internal sample, not an independent audit.

Data

Timeline

AWS reports intended-path success on 33 of 37 fresh vulnerability tests

AWS reports intended-path success on 33 of 37 fresh vulnerability tests

  1. · Occurred

    Publication of the research report

    AWS published an evaluation on October 15 testing its security agent, now part of AWS Continuum, on 37 disclosed vulnerabilities from 2025–2026. It captured 35 flags in isolated, containerized targets; the company’s per-sample trajectory audit confirmed that 33 were obtained through the intended vulnerability. The adjusted success rate was 89.2%.

Methodology

Reported research results are attributed to the source; no independent performance measurement was made.

Updated:

Table

AWS internal CVE evaluation counts

AWS internal CVE evaluation counts

Vulnerability targets tested37
Flags captured before audit35
Audited intended-path successes33
Captures reclassified as unintended-path2
Misses after target failure2
Methodology

Single-epoch results in AWS’s October 15 report: Claude Opus 5, 10 hours per sample. Two of 35 raw captures were excluded after audit for using another path; rows are not additive. No independent test was conducted.

Updated:

Structured coverage

Subjects and places

Subject proposals

Geographic references

Only source-provided geographic references are shown. Opening an external map is optional. Optional story maps use OpenStreetMap. Opening a map sends your IP address and this site’s address to the map provider; location data remains readable as text without loading the map.

  • United States · Place role: Coverage · Place type: Country or area · Location precision: Regional
    Evidence
    • Explicit preserved editorial country/region; no city or national centroid inferredaws.amazon.com ↗
Taxonomy version: IPTC Media Topics 2026-Q2

Continue reading

Technology

AWS links Continuum penetration tests to CI/CD deployment gates

An October 14 AWS technical post describes a security gate that uses Continuum to test changed code after staging deployment. Authentication uses OIDC; tests run in the AWS account, not on the CI runner.

AWS Security Blog1 min read Data included
Technology

AWS adds Availability Zone metadata to Lambda

AWS announced a metadata endpoint on October 9 that lets Lambda execution environments discover their Availability Zone ID. The information helps functions prefer resources in the same zone, such as ElastiCache nodes or database read replicas. AWS says the feature is available at no additional charge in every commercial Region offering Lambda.

AWS Compute Blog1 min read Data included