CVE-2024-23738: postman · n/a
Affects postmanSource CVE Database V5
Not known to be exploited.
Data as of 25 Oct 2026, 21:14 UTC
Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpostman/postmanpkg:github/postman/postmanOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor disputes the vulnerability's validity, indicating that no action may be necessary. Users should monitor official vendor communications for any updates or clarifications.
Description
A reported issue in Postman version 10.22 and earlier on macOS involves the RunAsNode and enableNodeClilnspectArguments settings, which allegedly could allow remote code execution. However, the vendor disputes the accuracy of this report, stating that the configuration does not enable remote code execution.