iana-time-zone vulnerable to use after free in MacOS / iOS implementation
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (iana-time-zone 0.1.45), 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
crates.io iana-time-zone
- Affected
- >= 0.1.43, < 0.1.45
- Fixed in
- 0.1.45
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3fg9-hcq5-vxrc lists affected ranges: crates.io iana-time-zone >=0.1.43 <0.1.45
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.
In iana-time-zone v0.1.43 a use-after-free bug in the MacOS / iOS implementation was introduced. The copied system time zone was released before its name was copied. If the system time zone was changed between the call of CFRelease and str::toowned(), random memory would be copied.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-3fg9-hcq5-vxrc
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-3fg9-hcq5-vxrc Advisory: iana-time-zone vulnerable to use after free in MacOS / iOS implementation IDs: GHSA-3fg9-hcq5-vxrc Record: https://patchnext.com/advisories/ghsa-3fg9-hcq5-vxrc (revision 1, source checked 26 Oct 2026, 15:33 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: iana-time-zone 0.1.45. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io iana-time-zone: affected >= 0.1.43, < 0.1.45; fixed in 0.1.45 ## Suggested inspection (read-only) - crates.io iana-time-zone: check the installed version with your package manager. ## 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 iana-time-zone. - 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://github.com/advisories/GHSA-3fg9-hcq5-vxrc (GitHub-reviewed advisory GHSA-3fg9-hcq5-vxrc lists affected ranges: crates.io iana-time-zone >=0.1.43 <0.1.45) Commands are suggestions: review each one before running it.
Loading voting…