Is there a public exploit for CVE-2023-5981?

No public exploit for CVE-2023-5981 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2023-5981?

CVE-2023-5981 scores CVSS 5.9 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 1.27%.

What does CVE-2023-5981 affect?

CVE-2023-5981 affects Red Hat RHOL-5.8-RHEL-9, RHODF-4.15-RHEL-9, Red Hat Enterprise Linux 9.2 Extended Update Support, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 8.6 Extended Update Support, Red Hat Enterprise Linux 8.

5.9 Medium

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of…

CVE-2023-5981

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.

Assessment

CVSS: 5.9 (v3.1)
Severity: Medium
EPSS: 1.27% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 28 November 2023
Last updated: 5 November 2026
Affected: Red Hat · RHODF-4.15-RHEL-9 · RHOL-5.8-RHEL-9 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 8.6 Extended Update Support
Assigner: redhat

CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 3 + 1? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2023-5981