NVD / CVE Program· CNA apache

CVE-2024-47248: Apache NimBLE: Buffer overflow in NimBLE MESH Bluetooth stack

Noroxi assessment

Priority: Monitor (action score 25/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.72% (FIRST EPSS); higher than 53.9% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Apache Software Foundation Apache NimBLE 1.8.0.

Low priority for now. Upgrade to Apache Software Foundation Apache NimBLE 1.8.0 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

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in Apache NimBLE. Specially crafted MESH message could result in memory corruption when non-default build configuration is used. This issue affects Apache NimBLE: through 1.7.0. Users are recommended to upgrade to version 1.8.0, which fixes the issue.

MediumCVSS 6.3 · v3.1—No exploit Fix available

Published: Nov 26, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 53th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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

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
apache	nimble	cpe:2.3:a:apache:nimble

Affected versions

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

apache nimblebefore 1.8.0

Versions reported by the vendor

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

Apache Software Foundation Apache NimBLE
- up to and including 1.7.0affected

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2026-45813Apache NimBLE: Incorrect data validation in BASS add/modify source operation
35Monitor
CVE-2025-62235Apache Mynewt NimBLE: Incorrect handling of SMP Security Request could lead to undesirable pairing
32Monitor
CVE-2026-45816Apache NimBLE: NULL pointer dereference vulnerability in SMP LTK request
30Monitor

Published before and after this one in the same product

← EarlierCVE-2024-24746Apr 6, 2024 · Apache NimBLE: Denial of service in NimBLE Bluetooth stack
30Monitor
Later →CVE-2024-47249Nov 26, 2024 · Apache NimBLE: Lack of input sanitization leading to out-of-bound reads in multiple advertisement handler
20Monitor
Later →CVE-2024-47250Nov 26, 2024 · Apache NimBLE: Lack of input validation in HCI advertising report could lead to potential out-of-bound access
20Monitor

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
Apache Software Foundation Apache NimBLE	1.8.0 · description	Vendor (CNA)

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.

apache/mynewt-nimblecommit 4f75c0b

Credits

All researchers

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

Wei Che Kao (Xiaobye), graduate studentNational Yang Ming Chiao Tung University, Dept. of CS, Security and Systems Lab.reporter

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

Someone on the same network segment 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: low · data can be read
Integrity: low · data or configuration can be modified
Availability: low · the service can be disrupted

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

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

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

nvd-secondary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

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

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

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

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/apache/mynewt-nimble/commit/4f75c0b3b466186beff40e8489870c6cee076aaa

Show all references (2 more)

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

All records