What happened
A public source linked this CVE to an advisory or demonstration repository. Review the original reference before use.
Affected versions
Unknown product: See original advisory Fixed: See vendor advisory.
Why it matters
This source correlation may provide earlier visibility while structured CVE metadata is still being updated.
Detection & mitigation
- Review the original advisory and validate affected versions.
- Apply vendor-provided updates or mitigations when available.
Public PoC references
RepositoryAuthorFirst seenReference
PoC-in-GitHub · FWNavy/RMASmokeRMASmoke main repo. CVE-2025-1122★ 2FWNavy2024-02-06CandidatePoC-in-GitHub · MCRideable3963/RMASmoke-v2RMASmoke main repo. CVE-2025-1122, (But better)★ 0MCRideable39632026-10-08CandidatePoC-in-GitHub · MCRideable3963/exploit-docsthe files/docs for various exploits, such as (LTBEEF, Sh1mmer, CryptoSmite, RMASmoke, aka: CVE-2025-1122, etc.)★ 2MCRideable39632026-10-09CandidatePoC-in-GitHub · ts2023dev/RMASmoke-v2RMASmoke main repo. CVE-2025-1122, (But better)★ 0ts2023dev2026-10-08CandidatePoC-in-GitHub · ts2023dev/exploit-docsthe files/docs for various exploits, such as (LTBEEF, Sh1mmer, CryptoSmite, RMASmoke, aka: CVE-2025-1122, etc.)★ 2ts2023dev2026-10-09CandidateSource timeline
Discovered through PoC-in-GitHubView source ↗
Record history
Record created from the first normalized source observation.
Metadata and source references refreshed.