dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2026-38740

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Foscam VD1 Video Doorbell before V5.3.13_1072 is vulnerable to Cleartext Transmission of Sensitive Information. The device transmits sensitive Session Description Protocol (SDP), including ICE credentials and candidates, in cleartext over network interfaces. An attacker with network visibility can intercept these credentials to hijack media streams or authenticate to Foscam's TURN/relay infrastructure to forward arbitrary traffic at the vendor's expense.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Foscam VD1 Video Doorbell transmits Session Description Protocol (SDP) data containing ICE credentials and candidates in cleartext over network interfaces prior to version V5.3.13_1072. An attacker with network visibility can intercept these credentials to hijack media streams or authenticate to Foscam's TURN/relay infrastructure.

MitigationUpdate the Foscam VD1 firmware to version V5.3.13_1072 or later. If immediate patching is not possible, restrict network access to trusted parties and monitor for unauthorized media stream interception.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the firmware version of the Foscam VD1
    Access the Foscam mobile app or the device web interface and navigate to Settings > Device Info > Firmware Version. Alternatively, check the device label or documentation.
    Affected if The firmware version is earlier than V5.3.13_1072, indicating the device is running a vulnerable version.
  2. Verify if unencrypted media streaming is enabled
    In the Foscam app or web interface, navigate to Network or Video settings and check whether encryption settings for live view or peer-to-peer streaming are disabled or set to optional.
    Affected if Encryption is disabled or optional, allowing cleartext transmission of media stream metadata.
  3. Inspect network traffic for cleartext SDP packets
    Use a network packet capture tool (such as Wireshark or tcpdump) on the local network to capture traffic to and from the doorbell's IP address. Filter for SIP or RTSP traffic and examine the SDP payload within the packets.
    Affected if SDP packets contain ICE candidates, usernames, and passwords transmitted in plaintext (not over TLS or DTLS).
  4. Check for direct peer-to-peer connection settings
    In the Foscam app settings, look for P2P or NAT traversal settings. If the device is configured to use automatic or easy connection modes without forced encryption, it may be using unencrypted paths.
    Affected if P2P or NAT traversal is enabled without explicit TLS/DTLS enforcement.

A defender is affected if their Foscam VD1 doorbell runs firmware earlier than V5.3.13_1072 and transmits unencrypted SDP data containing ICE credentials over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Foscam VD1 firmware to version V5.3.13_1072 or later. If immediate patching is not possible, restrict network access to trusted parties and monitor for unauthorized media stream interception.

Recommended fix Moderate confidence

V5.3.13_1072

  1. 1. Check the current firmware version of the Foscam VD1 Video Doorbell through the device management interface or Foscam mobile app
  2. 2. Navigate to the official Foscam support website or firmware download section
  3. 3. Download the fixed firmware version V5.3.13_1072 for the VD1 Video Doorbell
  4. 4. Access the device settings via web interface or mobile app and locate the firmware update section
  5. 5. Upload and apply the V5.3.13_1072 firmware update to the device
  6. 6. Verify the update was successful by confirming the new firmware version in the device settings
  7. 7. After updating, verify that media stream connections now use encrypted transmission (TLS/DTLS)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-38740 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data