ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-763v-5pjm-fx36

Strands Agents: Default FileSessionManager storage is world-readable on shared systems

Published Oct 27, 2026 · catalog updated Oct 27, 2026 · Strands Agents: Default FileSessionManager

Last checked Oct 28, 2026, 9 days ago.

Open the advisory

Exploitation likelihood is not on this record for GHSA-763v-5pjm-fx36. A missing EPSS score is not a low risk. Compare Strands Agents: Default FileSessionManager with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Strands Agents: Default FileSessionManager).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
pip strands-agents

There is a local confidentiality issue in the default storage behavior. By default it writes session data under and relies on the process umask for directory and file permissions. On systems using the common , the session directories are and JSON files are , so other local users can read persisted agent session data. This matters on shared developer machines, CI hosts, notebooks, jump boxes, and multi-user GPU servers. Session storage is intended to persist conversation/history/state, so it can contain prompts, model output, tool inputs/outputs, intermediate state, and secrets that pass through the agent. Relevant code: - : default storage path is . - : creates parent directories without a private mode. - : writes JSON files via normal . - : creates session directories without a private mode. Local reproduction with : The fixture wrote a fake secret into the session dict to show that sensitive session fields are readable through the resulting file. Suggested fixes: - Use a private per-user data directory by default rather than , or create and descendants with . - Write session JSON atomically with permissions. - Consider refusing to use an existing default storage directory if it is not owned by the current user or is group/world accessible. - Document that callers should set explicitly when they need shared storage. This was reproduced on commit .

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • pip strands-agents< 1.48.0

How to fix GHSA-763v-5pjm-fx36

  • Upgrade

    GHSA-763v-5pjm-fx36 lists a fix boundary at 1.48.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 1.48.0

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-763v-5pjm-fx36. A missing EPSS score is not a low risk. Compare Strands Agents: Default FileSessionManager with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with < 1.48.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-276: Incorrect Default Permissions. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · GitHub Advisory Database

    Detected

    There is a local confidentiality issue in the default storage behavior. By default it writes session data under and relies on the process umask for directory and file permissions. On systems using the common , the session directories are and JSON files are , so other local users can read persisted agent session data. This matters on shared developer machines, CI hosts, notebooks, jump boxes, and m

Sources

References

Freshness

Last verified in this catalog Oct 27, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 28, 2026