CVE-2017-16121: datachannel-client is a signaling implementation for DataChannel.js

Q: How do I fix CVE-2017-16121?

datachannel-client: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2017-16121 being exploited?

CVE-2017-16121 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-16121 affect?

CVE-2017-16121 affects datachannel-client. Severity is high (CVSS 7.5). datachannel-client is a signaling implementation for DataChannel.js. datachannel-client is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

Q: How urgent is CVE-2017-16121?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2017-16121 is a high-severity flaw (CVSS 7.5) affecting datachannel-client. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

datachannel-client is a signaling implementation for DataChannel.js. datachannel-client is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 20%)
CISA exploited list	No
Weakness	CWE-22
Published	2018-06-07
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: datachannel-client project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-07 02:29 UTCPublished CVE record published
2026-06-17 01:08 UTCUpdated Record last modified

datachannel-client project datachannel-client DOWNGRADE

Affected: 1.0.0 · 1.0.1 · 1.0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.0

1. Check installed version

npm ls datachannel-client

2. No fixed release: DOWNGRADE to a release before 1.0.0

npm view datachannel-client versions npm install datachannel-client@"<1.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-16121?

datachannel-client: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-16121 being exploited?

CVE-2017-16121 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-16121 affect?

CVE-2017-16121 affects datachannel-client. Severity is high (CVSS 7.5). datachannel-client is a signaling implementation for DataChannel.js. datachannel-client is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

How urgent is CVE-2017-16121?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs