Malicious URL drafting attack against iodines static file server may allow path traversal

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-22050: 0.92% estimated exploitation activity in the next 30 days; percentile 60.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A path traversal vulnerability was detected in iodine's static file service. This vulnerability effects any application running iodine's static file server on an effected iodine version. Malicious URL drafting may cause the static file server to attempt a response containing data from files that shouldn't be normally accessible from the public folder. Patches The vulnerability was patched in version 0.7.34. Please upgrade to the latest version. Workarounds A possible workaround would be to disable the static file service and it's X-Sendfile support, sending static files using nginx or a source code solution (sending the data dynamically). However, it would be better to upgrade iodine to the latest version, as it also contains non-security related fixes. For more information If you have any questions or comments about this advisory: Email Boaz Segev

Published by the source

7 Oct 2019, 16:52 UTC

Last modified by the source

15 Nov 2025, 03:10 UTC

Source last checked

26 Oct 2026, 15:51 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-85rf-xh54-whp3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-22050

Advisory: Malicious URL drafting attack against iodines static file server may allow path traversal
IDs: CVE-2024-22050, GHSA-85rf-xh54-whp3
Record: https://patchnext.com/advisories/cve-2024-22050 (revision 1, source checked 26 Oct 2026, 15:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: iodine 0.7.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems iodine: affected < 0.7.34; fixed in 0.7.34

## Suggested inspection (read-only)
- RubyGems iodine: 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 iodine.
- 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-85rf-xh54-whp3 (GitHub-reviewed advisory GHSA-85rf-xh54-whp3 lists affected ranges: RubyGems iodine >=0 <0.7.34)

Commands are suggestions: review each one before running it.