affected products in the CVE record: OpenSSL · OpenSSLCPE names NVD's analysts give as vulnerable: a:openssl:opensslthe product type of OpenSSL in nday's product registry
stage
DIS
disclosed
cvss
no score yet
# Lifecycle
x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet
# Summary
The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is 1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).
Original text of the CVE record (cvelist), shown as published.
Your account is suspended: you cannot comment, reply, edit or report. You can still delete your own comments.
formatting
↵↵
empty line: new paragraph
↵
line break: kept as is
*…*
emphasis
**…**
bold
`…`
inline code
```
on its own line: starts and ends a code block
> …
quote
- …
list
1. …
numbered list
[…](https://…)
link (http and https only)
https://…
bare address: link
CVE-2026-1234
links to that vulnerability on nday
\*
shows the character itself
Headings, images, tables, nested lists and HTML are shown as plain text.
Links from new accounts are shown as plain text; CVE IDs are always linked.
reported
# Keyboard shortcuts
j / k
next / previous row (list rows or events)
Enter
open the vulnerability under the cursor
/
search (Esc leaves the box)
y
copy the CVE ID
o
open the event's source (vulnerability page)
u
back
?
show / hide this help
sign inaccountmodadminAdminProfileFollowingSecurityDeveloperSign outSigned in.Sign-in method linked to your account.Sign-in was cancelled at the provider; nothing changed.That login already belongs to another nday account, or this account already has one from the same provider. Nothing was linked.Sign-in did not complete. Try again.You are still signed in as before: that login belongs to another nday account, or to none yet. Sign out first to use it.Linking was not completed because your last sign-in is no longer recent. Confirm it's you on the account page, then link again.This account is suspended, so new sign-in methods cannot be linked.Dismissworking…Delete this comment? This cannot be undone.Hidden by a moderator: {reason}text (moderators only)earlier versions: {n}replaced at {time}Posting needs the community rules accepted (version {version}).The community rules changed (version {version}); read and accept them to continue.Reported. A moderator will look at it.You have already reported this comment.You are signed out. Sign in again to continue.The request was refused as cross-site. Reload the page and try again.The session token changed. Reload the page and try again.Your account is suspended.Choose a handle on your account page first.Accept the current community rules first.Only moderators can do this.Only the author can do this.You cannot report your own comment.This comment changed in the meantime. Reload the page to see it as it is now.This comment or vulnerability does not exist (any more).Not a valid CVE ID.Only a visible top-level comment can get replies.This thread has reached its reply limit.You posted the same text here a moment ago.A comment needs 1 to {max} characters.Comments cannot be posted from this site language.Unknown purpose, or a purpose on a reply. Reload the page and try again.The reason is missing or too long.The note is too long.Unknown resolution.This position in the list is no longer valid. Reload the page.The request was malformed. Reload the page and try again.The text is too large.Too many requests. Try again in {seconds} s.Too many requests. Try again later.Daily limit reached. Try again after {time}.The server is busy. Try again in a moment.This address does not take comments. Open the page on the main site.Server error. Try again later.Network error: nday could not be reached. Check the connection and try again.The community rules changed while you were reading. Read them again.Write something first.Too long: {n} characters, at most {max}.Tick the box to accept the community rules first.Something went wrong ({code}). Try again.No comments yet.The discussion could not be loaded right now.more commentsfirst commentsmore repliesreplies[deleted account]link to this commenteditedposted on the {language} siteHidden by a moderator.Deleted by its author.technical analysisreproduction reportfix reportdetection methodquestionPlease include the affected version, the environment (OS, configuration), what you did and what happened, and your source.Please include the fixed version or patch, the environment, how you checked the fix and what happened, and your source.show {n} moreview on XThe posts could not be loaded.nday has not collected any post on X by listed researchers that mentions this CVE.expandcollapsesending…Sent. An editor will look at it; you can follow its status here.titlesummaryaffected products or versionsfix informationtimeline eventsource linksotherwaiting for an editoracceptednot acceptedsent {at}Editors' note: {note}Sign in first.Your account is suspended.Choose a public handle on your account page first.Accept the current community rules on your account page first.The page's session expired; try again.The request was refused; reload the page and try again.Choose what is wrong.Write what is wrong, within the length limit.The evidence link must be a full http:// or https:// address.You already have several reports on this vulnerability waiting for an editor; wait until they are handled.This vulnerability already has many reports waiting for an editor; try again later.You reached the limit of reports for 24 hours; try again later.Too many requests; wait a moment and try again.This vulnerability was not found.The report is too large.Network error; try again.Write what is wrong first.Too long: at most {max} characters.Something went wrong; try again later.