What is CVE-2026-19291?

CVE-2026-19291 is Bluetooth re-pairing can use a lower security level than previous. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-290 CWE-290.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-19291 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

3 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-19291 using CVSS 8.8, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highAuth Bypasspublic exploit

CVE-2026-19291

CVE-2026-19291 — Bluetooth re-pairing can use a lower security level than previous

Bluetooth re-pairing with an existing device can use a lower security level. RS9116W and SiWx91x impacted. See V3 in the BLERP paper linked below.

Published Aug 13, 2026Updated Aug 13, 2026Sources: NVD, silabs.com (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

ahead of 0% of scored CVEs

Affects

silabs.com

2 products listed

CVSS base

8.8

high

Remediation

The vendor's own words where we have them.

Upgrade WiseConnect to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
silabs.com	WiseConnect	4.0.0 to < 4.1.0	Vulnerable
silabs.com	WiseConnect	2.0.0 to < 2.14.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Adjacent

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	high	2.8	5.9	silabs.com (CNA), GHSA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-290 · Authentication Bypass by Spoofing

Bypass Protection Mechanism
Gain Privileges or Assume Identity

Weakness & attack patterns

CWE-290

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-21 · Exploitation of Trusted IdentifiersCAPEC-22 · Exploiting Trust in ClientCAPEC-459 · Creating a Rogue Certification Authority CertificateCAPEC-461 · Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-473 · Signature SpoofCAPEC-476 · Signature Spoofing by MisrepresentationCAPEC-59 · Session Credential Falsification through PredictionCAPEC-60 · Reusing Session IDs (aka Session Replay)CAPEC-94 · Man in the Middle Attack

T1134Access Token Manipulation
T1528Steal Application Access Token
T1539Steal Web Session Cookie

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 3 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

identity provider logsauthentication audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.8 (AV:A)
Aug 13, 2026 · NVD
Initial · CVE published
Aug 13, 2026 · NVD
Added · GHSA-8pg2-cp78-vjmv published (high)
Aug 13, 2026 · GitHub Security Advisory

References

6 on the record

community.silabs.com/068Vm00000x0yyH
Vendor Advisory
docs.silabs.com/rs9116-wiseconnect/latest/wifibt-wc-release-notes/rs9116-ble-release-notes#bug-fixes
Vendor Advisory
docs.silabs.com/sisdk-release-notes/latest/sisdk-wifi-release-notes/sisdk-wifible-ble-release-notes
Vendor Advisory
www.ndss-symposium.org/ndss-paper/blerp-ble-re-pairing-attacks-and-defenses/
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-19291
NVD
github.com/advisories/GHSA-8pg2-cp78-vjmv
Exploit, Third Party Advisory

Elsewhere on this site

silabs.comevery CVE for this vendor
Auth Bypasssame class
CWE-290other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-19291 is Bluetooth re-pairing can use a lower security level than previous, a high vulnerability affecting WiseConnect from silabs.com. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 3 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.