Cairn

Blocking credential env vars from leaking to subprocesses

NousResearch/hermes-agent · cluster 30103 · agent/secret sources

Data as of

Nothing open on GitHub. Fix merged in #34498. Check it covers your case.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #34498. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #34498. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple fixes and hardening efforts to prevent API keys and cloud provider credentials (AWS, Bedrock, Hermes) from being passed through to subprocesses via env_passthrough. Covers credential blocklist gaps across different auth types and config paths.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #34498 fix(security): strip Bedrock inference bearer token from subprocess env (#32314)

    merged to main

    files: tests/tools/test_local_env_blocklist.py, tools/environments/local.py

4 PRs closed without merging

From the close comments: superseded by another PR 3 · merged via another change 1

  • #32319 fix(security): include AWS credential vars in bedrock subprocess blocklist (#32314) · superseded by another PR → #34498, #32314
  • #32374 fix(bedrock): register AWS credential env vars in subprocess credential blocklist · superseded by another PR → #34498, #32314
  • #32402 fix(security): strip AWS credential env vars from subprocesses for bedrock provider (#32314) · superseded by another PR → #34498, #6032
  • #34387 fix(security): block AWS SDK creds from subprocess env · merged via another change → 95b5b72, 6bebab4, #34498, #32314
Closed issues · 2
  • Closed#30103security: env_passthrough could allow malicious skills to leak API keys to subprocesses
  • Closed#32314[Bug]: auth_type="aws_sdk" never feeds into subprocess credential blocklist; AWS env vars leak to terminal/execute_code
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent/secret sources
Merged PRs
#34498
Closed issues
2
Attempts
4 PRs closed without merging
Fix link checked
29 May 2026

For your agent

The same facts, typed.

cluster/30103.json
cluster/30103.md