Security readout for executives and security teams
Plain-English summary
CVE-2026-3706 concerns Dropbear SSH cryptographic signature verification in curve25519 code. Public sources rate it medium, but also state the vulnerability’s real-world existence is questioned. The maintainer says the reported signature malleability is not exploitable in the SSH protocol and relates to an internal API rather than an SSH proof of concept.
Executive priority
Treat as a planned remediation item, not an emergency, unless Dropbear is internet-facing or embedded in critical products. The practical SSH risk is disputed, but patching is prudent because the issue affects cryptographic verification logic.
Technical view
The report names function unpackneg in src/curve25519.c, component S Range Check, causing improper cryptographic signature verification. It is network-reachable with high attack complexity, no privileges, and limited integrity impact under CVSS 4.0 score 6.3. A referenced patch commit is fdec3c90a15447bd538641d85e5a3e3ac981011d.
Likely exposure
Exposure is most relevant where mkj Dropbear versions 2025.0 through 2025.89 are deployed. Validate embedded Linux, appliances, firmware, and systems using Dropbear SSH. Public data does not provide CPEs or downstream vendor package status.
Exploitation context
No active exploitation is supported by the provided sources, and KEV is false. VulDB says remote attack initiation is possible but difficult. The maintainer disputes practical SSH exploitability, stating no SSH implementation PoC exists and the issue targets an internal API.
Researcher notes
Key uncertainty is exploitability. Sources describe improper signature verification, but the maintainer states SSH protocol exploitation is not shown. Focus analysis on whether your deployed code exposes the affected internal API path or only standard Dropbear SSH behavior.
Mitigation direction
- Identify Dropbear deployments and versions, including embedded and appliance uses.
- Apply the referenced upstream patch where applicable.
- Check Dropbear and downstream vendor advisories for supported fixed releases.
- Prioritize internet-facing Dropbear services until vendor status is confirmed.
Validation and detection
- Confirm whether Dropbear is installed and externally reachable.
- Record exact Dropbear version and package source.
- Check whether commit fdec3c90a15447bd538641d85e5a3e3ac981011d is present.
- Review vendor firmware or OS advisories for backported fixes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3706 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.3MediumVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- VDB-349652 | mkj Dropbear S Range Check curve25519.c unpackneg signature verificationCVE reference · vdb-entry, technical-description
- VDB-349652 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #765933 | GitHub Dropbear 2025.89 Improper Verification of Cryptographic SignatureCVE reference · third-party-advisory
- https://github.com/mkj/dropbear/issues/406CVE reference · issue-tracking
- https://github.com/mkj/dropbear/pull/407CVE reference · issue-tracking, patch
- https://github.com/mkj/dropbear/commit/fdec3c90a15447bd538641d85e5a3e3ac981011dCVE reference · patch
- https://github.com/str4d/ed25519-java/issues/82#issue-727629226CVE reference · issue-tracking
- https://github.com/mkj/dropbear/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.