Skip to content
Applications

CVE-2018-25218

8.6
High
EPSS 0.21%Mar 26, 2026

SEH buffer overflow in PassFab RAR Password Recovery 9.3.2 enables local code execution via registration input.

common questions

Is CVE-2018-25218 being exploited?

Not confirmed. CVE-2018-25218 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2018-25218?

CVE-2018-25218 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2018-25218?

Not known from our data. No patch reference has been recorded for CVE-2018-25218, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2018-25218 affect?

CVE-2018-25218 affects PassFab RAR Password Recovery 9.3.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2018-25218?

Monitor for patch and upgrade to fixed version when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PassFab RAR Password Recovery 9.3.2
impact

Local arbitrary code execution via crafted payload in the registration field; requires app access.

action required

Patch when possible

affected versions
Passfab RAR Password Recovery
  • affected9.3.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free