CuraSec

tag: Aws · 2 items

2026-10-23 · HN (cve) · source ↗ #php#rce#aws
  • Engineer — Plan: Both CVEs have public PoCs on GitHub and AWS issued a bulletin, but neither is KEV-listed and EPSS scores (0.12/0.06) indicate limited active exploitation so far. Audit PHP runtime versions across Lambda functions and EC2 workloads, then schedule patching against the AWS bulletin guidance this sprint.
  • SOC/IR — Learn: Public PoCs exist but there are no reported IOCs, mapped TTPs, or confirmed in-the-wild exploitation campaigns to hunt or detect against; monitor threat feeds for escalation before building detections.
  • Leader — Skip
  • Signals: CVE-2026-109618 — CISA KEV: not listed, EPSS 0.12, public PoC on GitHub, reported by 5 collected sources · CVE-2026-109619 — CISA KEV: not listed, EPSS 0.06, public PoC on GitHub, reported by 5 collected sources
2026-08-22 · BleepingComputer · source ↗ #aws#credential-exposure#cloud-security
  • Engineer — Act: Still-valid exposed AWS keys require no exploitation sophistication — the credential is the exploit. Audit all active IAM access keys in your AWS accounts, cross-reference against the leaked dataset, rotate any keys created or last-used anomalously, and enforce least-privilege policies with automatic key rotation going forward.
  • SOC/IR — Act: Active leaked credentials mean unauthorized access may already be occurring. Hunt CloudTrail logs since August 2022 for API calls from unexpected source IPs, new IAM user/role creation, or unusual resource provisioning that could indicate keys were already abused by third parties.
  • Leader — Act: Hundreds of corporate AWS keys with full-account-control scope being publicly available for up to four years is a material risk requiring same-week action — confirm whether your organization’s keys appear in the exposed set and direct engineering to complete a credential audit and rotation before end of week.