CVE-2022-24719: Fluture-Node is a FP-style HTTP and streaming utils for Node based on Fluture

Q: How do I fix CVE-2022-24719?

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

Q: Is CVE-2022-24719 being exploited?

CVE-2022-24719 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-2022-24719 affect?

CVE-2022-24719 affects fluture-node. Severity is low (CVSS 2.6). Fluture-Node is a FP-style HTTP and streaming utils for Node based on Fluture. Using `followRedirects` or `followRedirectsWith` with any of the redirection strategies built into fluture-node 4.0.0 or 4.0.1, paired with a request that includ

Q: How urgent is CVE-2022-24719?

Priority 24/100. No elevated risk signals yet.

Routine

LOW 2.6DOWNGRADE

CVE-2022-24719 is a low-severity flaw (CVSS 2.6) affecting fluture-node. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Fluture-Node is a FP-style HTTP and streaming utils for Node based on Fluture. Using `followRedirects` or `followRedirectsWith` with any of the redirection strategies built into fluture-node 4.0.0 or 4.0.1, paired with a request that includes confidential headers such as Authorization or Cookie, exposes you to a vulnerability where, if the destination server were to redirect the request to a server on a third-party domain, or the same domain over

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	2.6 (Low)
Attack vector	Adjacent network
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 42%)
CISA exploited list	No
Weakness	CWE-359, CWE-212
Published	2022-03-01
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: fluture-node project

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

Am I affected?

Timeline

2022-03-01 21:15 UTCPublished CVE record published
2026-06-17 04:32 UTCUpdated Record last modified

fluture-node project fluture-node DOWNGRADE

Affected: 4.0.0 · 4.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.0.0

1. Check installed version

npm ls fluture-node

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

npm view fluture-node versions npm install fluture-node@"<4.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-2022-24719?

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

Is CVE-2022-24719 being exploited?

CVE-2022-24719 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-2022-24719 affect?

CVE-2022-24719 affects fluture-node. Severity is low (CVSS 2.6). Fluture-Node is a FP-style HTTP and streaming utils for Node based on Fluture. Using `followRedirects` or `followRedirectsWith` with any of the redirection strategies built into fluture-node 4.0.0 or 4.0.1, paired with a request that includ

How urgent is CVE-2022-24719?

Priority 24/100. No elevated risk signals yet.

References

← Back to latest CVEs