NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2023-43116 — elastic-ci-stack-for-aws

HIGHFix: buildkite/elastic-ci-stack-for-aws@8f79882

CVE-2023-43116 is a high-severity (CVSS 7.8) CWE-59 vulnerability in github.com/buildkite/elastic-ci-stack-for-aws/v6. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/buildkite/elastic-ci-stack-for-aws/v6 — see the affected versions and patch details below.

Buildkite Elastic CI for AWS symbolic link following vulnerability

Also known asGHSA-7c44-7j7v-w554
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk
0.00%0.28%0.55%0.83%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/buildkite/elastic-ci-stack-for-aws/v6

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A symbolic link following vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to change ownership of arbitrary directories via the PIPELINE_PATH variable in the fix-buildkite-agent-builds-permissions script.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/buildkite/elastic-ci-stack-for-aws/v6all versions6.7.0go get github.com/buildkite/elastic-ci-stack-for-aws/v6@v6.7.0

Affected Products

1 product · 2 configurations
Application
elastic ci stackbuildkite
≥ 6.0.0 && < 6.7.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A symbolic link following vulnerability in Buildkite Elastic CI for AWS …

github.comNVDJan 2024

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/buildkite/elastic-ci-stack-for-aws/v6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/buildkite/elastic-ci-stack-for-aws/v6 to 6.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-43116 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

A symbolic link following vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to change ownership of arbitrary directories via the PIPELINE_PATH variable in the fix-buildkite-agent-builds-permissions script.
O3 Security · Impact-Aware SCA

Is CVE-2023-43116 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-43116: elastic-ci-stack-for-aws — Fixed in 6.7.0