CVE-2023-26942Public exploit

Alarm access via default-key RFID tag cloning

Published Dec 4, 2023 · Updated Aug 2, 2024

RFID authentication weakness in Yale IA-210 Alarm 1.0 allows physically proximate attackers to clone a tag and access the alarm. The MIFARE Classic tag uses the factory-default FFFFFFFFFFFF key, while the alarm relies on the UUID stored in the tag's first block. Brief proximity to an enrolled tag permits copying that UUID into the corresponding block of a blank card, which the alarm accepts as the original credential.

CVSS severity6.5
Medium
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

RFID authentication weakness in Yale IA-210 Alarm 1.0 allows physically proximate attackers to clone a tag and access the alarm. The MIFARE Classic tag uses the factory-default FFFFFFFFFFFF key, while the alarm relies on the UUID stored in the tag's first block. Brief proximity to an enrolled tag permits copying that UUID into the corresponding block of a blank card, which the alarm accepts as the original credential.

The record

CVE
CVE-2023-26942
Published
Dec 4, 2023
Updated
Aug 2, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-326
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 4, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-326Inadequate Encryption Strength

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo