CVE-2018-25332
Unauthenticated RCE in GitBucket 4.23.1 via weak token and file upload.
Is CVE-2018-25332 being exploited?
Not confirmed. CVE-2018-25332 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.59% probability of exploitation in the next 30 days.
How severe is CVE-2018-25332?
CVE-2018-25332 is rated Critical with a CVSS score of 9.3. 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-25332?
Yes. A fix has been recorded for CVE-2018-25332. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2018-25332 affect?
CVE-2018-25332 affects GitBucket 4.23.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2018-25332?
Upgrade to latest GitBucket or apply fixes; tighten upload/token controls.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via brute-forcible Blowfish key and exploit endpoint; attacker can run arbitrary commands.
Immediate action required
- affected4.23.1
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.