Cleartext Transmission of Sensitive Information in moment-timezone
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (moment-timezone 0.5.35), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm moment-timezone
- Affected
- >= 0.1.0, < 0.5.35
- Fixed in
- 0.5.35
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-v78c-4p63-2j6c lists affected ranges: npm moment-timezone >=0.1.0 <0.5.35 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v78c-4p63-2j6c lists affected ranges: npm moment-timezone >=0.1.0 <0.5.35
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact if Alice uses grunt data (or grunt release) to prepare a custom-build, moment-timezone with the latest tzdata from IANA's website and Mallory intercepts the request to IANA's unencrypted ftp server, Mallory can serve data which might exploit further stages of the moment-timezone tzdata pipeline, or potentially produce a tainted version of moment-timezone (practicality of such attacks is not proved) Patches Problem has been patched in version 0.5.35, patch should be applicable with minor modifications to all affected versions. The patch includes changing the FTP endpoint with an HTTPS endpoint. Workarounds Specify the exact version of tzdata (like 2014d, full command being grunt data:2014d, then run the rest of the release tasks by hand), or just apply the patch before issuing the grunt command.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-v78c-4p63-2j6c
- Revision 1 · created ·
Published from osv record GHSA-v78c-4p63-2j6c
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-v78c-4p63-2j6c Advisory: Cleartext Transmission of Sensitive Information in moment-timezone IDs: GHSA-v78c-4p63-2j6c Record: https://patchnext.com/advisories/ghsa-v78c-4p63-2j6c (revision 2, source checked 26 Oct 2026, 12:16 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: moment-timezone 0.5.35. A vendor fix does not mean a deployment is fixed. ## Affected components - npm moment-timezone: affected >= 0.1.0, < 0.5.35; fixed in 0.5.35 ## Suggested inspection (read-only) - `npm ls moment-timezone --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on moment-timezone. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-v78c-4p63-2j6c (OSV record GHSA-v78c-4p63-2j6c lists affected ranges: npm moment-timezone >=0.1.0 <0.5.35 (fixed)) - Verified: https://github.com/advisories/GHSA-v78c-4p63-2j6c (GitHub-reviewed advisory GHSA-v78c-4p63-2j6c lists affected ranges: npm moment-timezone >=0.1.0 <0.5.35) Commands are suggestions: review each one before running it.
Loading voting…