dbcve.org
Iterm2Application

CVE-2025-22275

CRITICAL · 9.3 CVSS v3.1 Published 2025-01-03
Fix available
A fix is available. Upgrade to 3.5.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
iTerm2 3.5.6 through 3.5.10 before 3.5.11 sometimes allows remote attackers to obtain sensitive information from terminal commands by reading the /tmp/framer.txt file. This can occur for certain it2ssh and SSH Integration configurations, during remote logins to hosts that have a common Python installation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an information disclosure vulnerability in iTerm2's SSH Integration feature (it2ssh). When using certain SSH Integration configurations with hosts that have common Python installations, sensitive terminal command output gets written to /tmp/framer.txt, which remote attackers can read to obtain credentials, API keys, or other sensitive data transmitted during the SSH session.

MitigationUpdate iTerm2 to version 3.5.11 or later. As a temporary workaround, restrict access to /tmp/framer.txt or monitor for unauthorized access to that file.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Iterm2Application
Affected:>= 3.5.6, < 3.5.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your iTerm2 version
    Open iTerm2 and go to iTerm2 > About iTerm2, or run `grep -i iterm /Applications/iTerm.app/Contents/Info.plist 2>/dev/null` or check via Homebrew: `brew list --cask iterm2` and compare version to affected range 3.5.6 through 3.5.10
    Affected if The installed version is 3.5.6, 3.5.7, 3.5.8, 3.5.9, or 3.5.10 (any version >= 3.5.6 but < 3.5.11)
  2. Verify SSH Integration is configured
    Inspect your iTerm2 profiles: go to Profiles > Open Profiles > Edit Profiles, and check if any profile has SSH Integration (it2ssh) enabled under the "SSH Integration" tab, or search for it2ssh configuration files in your home directory
    Affected if SSH Integration (it2ssh) is enabled in any iTerm2 profile
  3. Inspect /tmp/framer.txt for sensitive data
    Run `ls -la /tmp/framer.txt` to check if the file exists, then `cat /tmp/framer.txt` to examine its contents for credentials, API keys, or terminal output
    Affected if The file /tmp/framer.txt exists and contains sensitive information such as passwords, tokens, or command output from SSH sessions
  4. Check file permissions on /tmp/framer.txt
    Run `ls -la /tmp/framer.txt` and verify if the file is readable by other users (permissions should not show world-readable or group-readable access beyond owner)
    Affected if The file is readable by other users (permissions include 'r--r--r--' or similar world-readable bits)

You are affected if iTerm2 version is between 3.5.6 and 3.5.10 inclusive AND SSH Integration is enabled AND /tmp/framer.txt contains sensitive data from your SSH sessions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.5.11 or later
Fixed in 3.5.11
Interim mitigation

Update iTerm2 to version 3.5.11 or later. As a temporary workaround, restrict access to /tmp/framer.txt or monitor for unauthorized access to that file.

Recommended fix High confidence

iTerm2 3.5.11

  1. 1. Verify current iTerm2 version by selecting iTerm2 > About iTerm2 from the menu
  2. 2. If running version 3.5.6 through 3.5.10, download iTerm2 version 3.5.11 or later from iterm2.com/downloads
  3. 3. Install the new version by dragging the iTerm app to the Applications folder
  4. 4. Restart iTerm2 to ensure the updated version is running
  5. 5. If using it2ssh or SSH Integration, verify that /tmp/framer.txt is no longer being created or contains sensitive data

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iterm2 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22275 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data