Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 15 January 2026.
- Which products and versions are affected?
- AWS aws-sdk-js-v3; AWS aws-lc; AWS amazon-corretto-crypto-provider; AWS (awslabs) open-data-registry.
- Is there a fix for This vulnerability?
- A patch was published on 2026-01-15: AWS confirmed remediation of all reported concerns Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Amazon AWS, AWS Corretto Crypto Provider, AWS LC or one of the others listed. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability stems from insufficient regular expression anchoring in AWS CodeBuild webhook filters for specific GitHub repositories. These filters were intended to restrict build triggers to trusted ACTOR_ID values, but the unanchored regex allowed attackers to bypass the restriction by using a predictably acquired actor ID that matched the weak pattern. If exploited, an attacker could gain administrative permissions for the affected repositories, enabling them to commit unauthorized code or access build-time secrets. AWS mitigated the issue by correcting the regex patterns, rotating credentials, and auditing CloudTrail logs to confirm no malicious exploitation occurred.
Affected products
- AWS aws-sdk-js-v3
- AWS aws-lc
- AWS amazon-corretto-crypto-provider
- AWS (awslabs) open-data-registry
Timeline
- 2026-01-15: advisory: Bulletin 2026-002-AWS published
- 2026-01-15: patched: AWS confirmed remediation of all reported concerns