Exploited CVEs / GNU / CVE-2014-6278

CVE-2014-6278

GNU Bash OS Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2025-10-23 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV

8.8

CVSS base

100%

EPSS exploit probability

High

Severity

2025-10-02

Added to KEV

2025-10-23 (past due)

CISA due date

Actively exploited GNU Bash vulnerability, High severity, CVSS 8.8. Added to the CISA KEV catalog 2025-10-02.

Senserva AI read on CVE-2014-6278 CISA required action Official fix for CVE-2014-6278 Admin questions

Senserva AI Opinion for CVE-2014-6278

Part of the Shellshock family, this GNU Bash flaw executes attacker commands via a crafted environment and scores a 100 percent EPSS probability. What stands out is the timing: CISA added it to KEV in October 2025, more than a decade after disclosure, meaning attackers still find unpatched Bash in the wild. Anything that passes untrusted input into Bash environments, old CGI stacks especially, is the exposure.

Do this: Scan servers and appliances for ancient Bash versions, including embedded devices that never received a Shellshock fix.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2014-6278

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2014-6278, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2014-6278.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2014-6278: GNU Bash OS Command Injection Vulnerability
- Affected: GNU Bash
- Severity: High, CVSS 8.8; EPSS 30-day exploitation probability 100%
- Added to CISA KEV: 2025-10-02; federal remediation due 2025-10-23
- Ransomware-linked: no
- CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Federal remediation deadline 2025-10-23; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2014-6278

Published: 2025-10-02
Last revised: 2025-10-02
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2025-10-02 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 8.8; EPSS first scored at 99.6%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2025-10-23 (past due).

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Official fix for CVE-2014-6278

Check the vendor's security advisory channel for the patched GNU Bash versions and workarounds.

CISA KEV entry

Common questions about CVE-2014-6278

Is CVE-2014-6278 actively exploited?

Yes. CVE-2014-6278 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2025-10-02, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%.

What is the CISA deadline and required action for CVE-2014-6278?

CISA set the federal (BOD 22-01) remediation due date at 2025-10-23, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2014-6278?

Check the vendor's security advisory for the patched GNU Bash versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2014-6278?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2014-6278's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited GNU CVEs: CVE-2026-24061 CVE-2023-4911 CVE-2014-6271 CVE-2014-7169
All GNU exploited CVEs on one page: GNU vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.