CVE-2026-25963: Fleet: Authorization Bypass in certificate template batch deletion for team administrators
Noroxi assessment
Priority: Monitor (action score 4/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: 0.20% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are 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.
- Fixed version: github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1.
Low priority for now. Upgrade to github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1 or later.
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
Fleet is open source device management software. In versions prior to 4.80.1, a broken authorization check in Fleet’s certificate template deletion API could allow a team administrator to delete certificate templates belonging to other teams within the same Fleet instance. Fleet supports certificate templates that are scoped to individual teams. In affected versions, the batch deletion endpoint validated authorization using a user-supplied team identifier but did not verify that the certificate template IDs being deleted actually belonged to that team. As a result, a team administrator could delete certificate templates associated with other teams, potentially disrupting certificate-based workflows such as device enrollment, Wi-Fi authentication, VPN access, or other certificate-dependent configurations for the affected teams. This issue does not allow privilege escalation, access to sensitive data, or compromise of Fleet’s control plane. Impact is limited to integrity and availability of certificate templates across teams. Version 4.80.1 patches the issue. If an immediate upgrade is not possible, administrators should restrict access to certificate template management to trusted users and avoid delegating team administrator permissions where not strictly required.
- Published
- Feb 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-863
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 1.2
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
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
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
|---|---|---|
| fleetdm | fleet | cpe:2.3:a:fleetdm:fleet |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fleetdm fleetbefore 4.80.1
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.
fleetdm fleet
- < 4.80.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/fleetdm/fleet/v4 | before 4.80.1 | 4.80.1 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20260317T205859-150000.1.152.1 | 0.0.20260317T205859-150000.1.152.1 |
Same product
fleetdm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-26276SAML authentication vulnerability in Fleet40Plan
- CVE-2026-103264Fleet before 4.87.0 Authentication Bypass via Device Identifiers37Monitor
- CVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-23999Feb 25, 2026 · Fleet: Device lock PIN can be predicted if lock time is known2Monitor
- ← EarlierCVE-2026-24004Feb 25, 2026 · Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint6Monitor
- Later →CVE-2026-27465Feb 25, 2026 · Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users5Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/fleetdm/fleet/v4 | 4.80.1 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20260317T205859-150000.1.152.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
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 researchersFinders, 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.
- CVE-2026-103265218 days apartFleet before 4.89.0 Information Disclosure via MDM Command Results21Monitor
- CVE-2026-41262182 days apartFleet: Cross-Team Policy Data Exposure via Global Policy Read Endpoint17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.