Howyar UEFI Application "Reloader" (32-bit and 64-bit) is vulnerable to execution of unsigned software in a hardcoded path.
Noroxi assessment
Priority: Monitor (action score 32/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.6% of all records.
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Windows 10 for 32-bit Systems 10.0.10240.20890; Windows 10 for x64-based Systems 10.0.10240.20890; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.7699.
Low priority for now. Upgrade to Windows 10 for 32-bit Systems 10.0.10240.20890; Windows 10 for x64-based Systems 10.0.10240.20890; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.7699 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
- Published
- Jan 14, 2025
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 64th percentile
- CWE
- CWE-347
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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
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 helpAffected 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 |
|---|---|---|
| howyar | sysreturn | cpe:2.3:a:howyar:sysreturn |
| cs-grp | neo impact | cpe:2.3:a:cs-grp:neo_impact |
| greenware | greenguard | cpe:2.3:a:greenware:greenguard |
| radix | smart recovery | cpe:2.3:a:radix:smart_recovery |
| sanfong | ez-back system | cpe:2.3:a:sanfong:ez-back_system |
| signalcomputer | hdd king | cpe:2.3:a:signalcomputer:hdd_king |
| wasay | erecoveryrx | cpe:2.3:a:wasay:erecoveryrx |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cs-grp neo impactbefore 10.1.024-20241127
- greenware greenguardbefore 10.2.023-20240927
- howyar sysreturnbefore 10.2.023_20240919
- radix smart recoverybefore 11.2.023-20240927
- sanfong ez-back systembefore 10.3.024-20241127
- signalcomputer hdd kingbefore 10.3.021-20241127
- wasay erecoveryrxbefore 8.4.022-20241127
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
CES Taiwan CES NeoImpact
- before 10.1.024-20241127affected
Greenware Technologies GreenGuard
- before 10.2.023-20240927affected
Howyar Technologies SysReturn (32-bit and 64-bit)
- before 10.2.02320240919affected
Radix SmartRecovery
- before 11.2.023-20240927affected
SANFONG SANFONG EZ-Back System
- before 10.3.024-20241127affected
SignalComputer HDD King
- before 10.3.021-20241127affected
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 |
|---|---|---|
| Windows 10 for 32-bit Systems | 10.0.10240.20890 · KB5050013 | Microsoft (MSRC) |
| Windows 10 for x64-based Systems | 10.0.10240.20890 · KB5050013 | Microsoft (MSRC) |
| Windows 10 Version 1607 for 32-bit Systems | 10.0.14393.7699 · KB5049993 | Microsoft (MSRC) |
| Windows 10 Version 1607 for x64-based Systems | 10.0.14393.7699 · KB5049993 | Microsoft (MSRC) |
| Windows 10 Version 1809 for 32-bit Systems | 10.0.17763.6775 · KB5050008 | Microsoft (MSRC) |
| Windows 10 Version 1809 for x64-based Systems | 10.0.17763.6775 · KB5050008 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for 32-bit Systems | 10.0.19044.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for ARM64-based Systems | 10.0.19044.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for x64-based Systems | 10.0.19044.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for 32-bit Systems | 10.0.19045.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for ARM64-based Systems | 10.0.19045.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for x64-based Systems | 10.0.19045.5371 · KB5049981 | Microsoft (MSRC) |
| Windows 11 Version 22H2 for ARM64-based Systems | 10.0.22621.4751 · KB5050021 | Microsoft (MSRC) |
| Windows 11 Version 22H2 for x64-based Systems | 10.0.22621.4751 · KB5050021 | Microsoft (MSRC) |
| Windows 11 Version 23H2 for ARM64-based Systems | 10.0.22631.4751 · KB5050021 | Microsoft (MSRC) |
| Windows 11 Version 23H2 for x64-based Systems | 10.0.22631.4751 · KB5050021 | Microsoft (MSRC) |
| Windows 11 Version 24H2 for ARM64-based Systems | 10.0.26100.2894 · KB5050009 | Microsoft (MSRC) |
| Windows 11 Version 24H2 for x64-based Systems | 10.0.26100.2894 · KB5050009 | Microsoft (MSRC) |
| Windows Server 2012 | 6.2.9200.25273 · KB5050004 | Microsoft (MSRC) |
| Windows Server 2012 (Server Core installation) | 6.2.9200.25273 · KB5050004 | Microsoft (MSRC) |
| Windows Server 2012 R2 | 6.3.9600.22371 · KB5050048 | Microsoft (MSRC) |
| Windows Server 2012 R2 (Server Core installation) | 6.3.9600.22371 · KB5050048 | Microsoft (MSRC) |
| Windows Server 2016 | 10.0.14393.7699 · KB5049993 | Microsoft (MSRC) |
| Windows Server 2016 (Server Core installation) | 10.0.14393.7699 · KB5049993 | Microsoft (MSRC) |
| Windows Server 2019 | 10.0.17763.6775 · KB5050008 | Microsoft (MSRC) |
| Windows Server 2019 (Server Core installation) | 10.0.17763.6775 · KB5050008 | Microsoft (MSRC) |
| Windows Server 2022 | 10.0.20348.3091 · KB5049983 | Microsoft (MSRC) |
| Windows Server 2022 (Server Core installation) | 10.0.20348.3091 · KB5049983 | Microsoft (MSRC) |
| Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.1369 · KB5049984 | Microsoft (MSRC) |
| Windows Server 2025 | 10.0.26100.2894 · KB5050009 | Microsoft (MSRC) |
+1
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-02-08 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-06-15 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-11 |
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.
- Published
- First PoC+390 d
- TodayOct 22, 2026+646 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Martin SmolarESET
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 with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, { algorithms: ["RS256"], issuer: "https://id.example.com", audience: "portal",});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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.