CVE-2025-1146: CrowdStrike Falcon Sensor for Linux TLS Issue
Noroxi assessment
Priority: Monitor (action score 32/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.26% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: CrowdStrike Falcon Container Sensor 7.06.4705, 7.10.4907, 7.11.5003; CrowdStrike Falcon Kubernetes Admission Controller 7.06.603, 7.10.806, 7.11.904; CrowdStrike Falcon sensor for Linux 7.06.16113, 7.07.16209, 7.10.16321.
Low priority for now. Upgrade to CrowdStrike Falcon Container Sensor 7.06.4705, 7.10.4907, 7.11.5003; CrowdStrike Falcon Kubernetes Admission Controller 7.06.603, 7.10.806, 7.11.904; CrowdStrike Falcon sensor for Linux 7.06.16113, 7.07.16209, 7.10.16321 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
CrowdStrike uses industry-standard TLS (transport layer security) to secure communications from the Falcon sensor to the CrowdStrike cloud. CrowdStrike has identified a validation logic error in the Falcon sensor for Linux, Falcon Kubernetes Admission Controller, and Falcon Container Sensor where our TLS connection routine to the CrowdStrike cloud can incorrectly process server certificate validation. This could allow an attacker with the ability to control network traffic to potentially conduct a man-in-the-middle (MiTM) attack. CrowdStrike identified this issue internally and released a security fix in all Falcon sensor for Linux, Falcon Kubernetes Admission Controller, and Falcon Container Sensor versions 7.06 and above. CrowdStrike identified this issue through our longstanding, rigorous security review process, which has been continually strengthened with deeper source code analysis and ongoing program enhancements as part of our commitment to security resilience. CrowdStrike has no indication of any exploitation of this issue in the wild. CrowdStrike has leveraged its world class threat hunting and intelligence capabilities to actively monitor for signs of abuse or usage of this flaw and will continue to do so. Windows and Mac sensors are not affected by this.
- Published
- Feb 12, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-296
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CrowdStrike
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
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 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.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CrowdStrike). Independent of NVD's CPE analysis and usually ahead of it.
CrowdStrike Falcon Container Sensor
- 7.21.6003not affected
- 7.20 and later · before 7.20.5908affected · semver
- 7.19 and later · before 7.19.5807affected · semver
- 7.18 and later · before 7.18.5705affected · semver
- 7.17 and later · before 7.17.5603affected · semver
- 7.16 and later · before 7.16.5503affected · semver
- 7.15 and later · before 7.15.5403affected · semver
- 7.14 and later · before 7.14.5306affected · semver
- 7.13 and later · before 7.13.5202affected · semver
- 7.12 and later · before 7.12.5102affected · semver
CrowdStrike Falcon Kubernetes Admission Controller
- 7.21.1904not affected
- 7.20 and later · before 7.20.1808affected · semver
- 7.18 and later · before 7.18.1605affected · semver
- 7.17 and later · before 7.17.1503affected · semver
- 7.16 and later · before 7.16.1403affected · semver
- 7.14 and later · before 7.14.1203affected · semver
- 7.13 and later · before 7.13.1102affected · semver
- 7.12 and later · before 7.12.1002affected · semver
- 7.11 and later · before 7.11.904affected · semver
- 7.10 and later · before 7.10.806affected · semver
CrowdStrike Falcon sensor for Linux
- 7.21.17405not affected
- 7.20 and later · before 7.20.17308affected · semver
- 7.19 and later · before 7.19.17221affected · semver
- 7.18 and later · before 7.18.17131affected · semver
- 7.17 and later · before 7.17.17014affected · semver
- 7.16 and later · before 7.16.16909affected · semver
- 7.15 and later · before 7.15.16806affected · semver
- 7.14 and later · before 7.14.16705affected · semver
- 7.13 and later · before 7.13.16606affected · semver
- 7.11 and later · before 7.11.16410affected · semver
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 |
|---|---|---|
| CrowdStrike Falcon Container Sensor | 7.06.4705 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.10.4907 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.11.5003 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.12.5102 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.13.5202 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.14.5306 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.15.5403 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.16.5503 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.17.5603 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.18.5705 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.19.5807 | Vendor (CNA) |
| CrowdStrike Falcon Container Sensor | 7.20.5908 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.06.603 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.10.806 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.11.904 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.12.1002 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.13.1102 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.14.1203 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.16.1403 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.17.1503 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.18.1605 | Vendor (CNA) |
| CrowdStrike Falcon Kubernetes Admission Controller | 7.20.1808 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.06.16113 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.07.16209 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.10.16321 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.11.16410 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.13.16606 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.14.16705 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.15.16806 | Vendor (CNA) |
| CrowdStrike Falcon sensor for Linux | 7.16.16909 | Vendor (CNA) |
+4
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.
No nightly-computed relations.
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.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-296 · Improper Following of a Certificate's Chain of TrustCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.