# CVE-2026-112407: Incorrect privilege assignment in AWS CICD-toolchain-for-serverless-applications


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-f76m-4xrx-pvq5

## What is CVE-2026-112407?

CVE-2026-112407 is a high-severity vulnerability in AWS CICD-toolchain-for-serverless-applications, published on 20 Oct 2026. 

### Official description

Incorrect privilege assignment in the IAM policy of AWS CICD-toolchain-for-serverless-applications 1.0.7 through 1.0.10 allows remote authenticated users with push access to the application source repository to escalate privileges and access or modify resources outside the application stack in the same AWS account via application templates deployed by the toolchain pipeline.

To remediate this issue, users should upgrade existing toolchain stacks to version 1.0.11 or later.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-112407?


## How do I fix CVE-2026-112407?

No fix has been published for CVE-2026-112407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112407 being exploited?

There is no known exploitation of CVE-2026-112407 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112407 and fix it if it is affected.

What it is: CVE-2026-112407 is a high-severity vulnerability in AWS CICD-toolchain-for-serverless-applications, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112407 in the wild and no public exploit code.

Affected product: AWS CICD-toolchain-for-serverless-applications. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112407/ (Markdown: https://insights.sbomify.com/CVE-2026-112407/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112407
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112407
- OSV: https://osv.dev/vulnerability/CVE-2026-112407

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112407/
Summaries are generated and may contain mistakes; the official description above is the record.