NVD / CVE Program· CNA GitHub_M

CVE-2021-43832: Improper Access Control in spinnaker

Noroxi assessment

Priority: Plan (action score 40/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.6% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Spinnaker is an open source, multi-cloud continuous delivery platform. Spinnaker has improper permissions allowing pipeline creation & execution. This lets an arbitrary user with access to the gate endpoint to create a pipeline and execute it without authentication. If users haven't setup Role-based access control (RBAC) with-in spinnaker, this enables remote execution and access to deploy almost any resources on any account. Patches are available on the latest releases of the supported branches and users are advised to upgrade as soon as possible. Users unable to upgrade should enable RBAC on ALL accounts and applications. This mitigates the ability of a pipeline to affect any accounts. Block application access unless permission are enabled. Users should make sure ALL application creation is restricted via appropriate wildcards.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Published: Jan 4, 2022
Updated: Jun 17, 2026
EPSS: 2.6% · 85th percentile
CWE: CWE-306

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · GitHub_M: 10.0; 0.2 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linuxfoundation	spinnaker	cpe:2.3:a:linuxfoundation:spinnaker

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linuxfoundation spinnakerbefore 1.25.8
linuxfoundation spinnaker1.26.0 and later · before 1.26.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

spinnaker spinnaker
- >= 1.26.0, < 1.26.7, < 1.25.8affected

Same product

linuxfoundation: all records

Other highest-scoring records for the same primary product.

CVE-2026-32613Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling
39Monitor
CVE-2026-32604Spinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths
39Monitor
CVE-2026-44795Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types
35Monitor

Published before and after this one in the same product

← EarlierCVE-2020-9301Dec 10, 2020 · Nolan Ray from Apple Information Security identified a security vulnerability in Spinnaker, all versions prior to version 1.23.4, 1.22.4 or
35Monitor
← EarlierCVE-2021-39143Jan 4, 2022 · Path Traversal in spinnaker
28Monitor
Later →CVE-2022-23506Jan 3, 2023 · Spinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer builds
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2021-391430 days apartPath Traversal in spinnaker
28Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-306 · Missing Authentication for Critical Function

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

The bug in code

The whole CWE-306 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1// Added for the support team
2app.post("/maintenance/reset", resetDevice);

Fixed

1if (config.maintenanceEnabled) {
2  app.post(
3    "/maintenance/reset",
4    requireSession, requireRole("admin"), resetDevice
5  );
6}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

github.com/spinnaker/spinnaker/security/advisories/GHSA-9h7c-rfrp-gvgp

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records