Skip to content

Potential Security Risk: Claude Code Accessing Local .env File Environment Variables #112

New issue
New issue
Closed as duplicate
Closed as duplicate
Potential Security Risk: Claude Code Accessing Local .env File Environment Variables#112

Description

@ohmaseclaro
ohmaseclaro
opened on Feb 26, 2025

Bug Description
apparentely, claude code uses my .env in my node.js project as if it was yours. I see that because I have DEBUG=true in my .env, which causes claude code to post debug logs about the requests it's doing. not only it seems to be not intended, but it also raises security concerns about claude code reading my keys

Environment Info

  • Platform: macos
  • Terminal: vscode
  • Version: 0.2.14
  • Feedback ID: 40b8e089-d871-43e4-9f12-e5bd80984280

Activity

  1. bcherny
    closed this as a duplicateof How to tell claude CLI agent to ignore directories (i.e. is there a ".claudeignore"?) #79 on Feb 26, 2025

  2. github-actions commented on Aug 9, 2025

    @github-actions
    github-actionsBot
    on Aug 9, 2025 – with GitHub Actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  3. github-actions
    locked as resolved and limited conversation to collaborators on Aug 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions