Skip to content

Security Alert: tmp allows arbitrary temporary file / directory write via symbolic link dir parameter #255

Closed

Description

@akaustav

The version of the tmp package currently used in this repository is vulnerable to the security issue described in:

And here's a sample outcome of the npm ls tmp command ran in a temporary project using v0.16.5 of apigeetool:

% npm ls tmp
project@1.0.0 /path/to/project
└─┬ apigeetool@0.16.5
  └── tmp@0.0.27

Please fix this.

Activity

  1. akaustav commented on Dec 9, 2025

    @akaustav
    ContributorAuthor

    I believe the issue comes from the following line:

    "tmp": "^0.0.27"

  2. akaustav commented on Jan 1, 2026

    @akaustav
    ContributorAuthor

    @DinoChiesa - I have opened PR #256 with a potential fix for this issue. However, I have NOT tested the changes from that PR in a real Apigee Edge environment yet.

  3. akaustav commented on Feb 24, 2026

    @akaustav
    ContributorAuthor

    @DinoChiesa - Gentle reminder about this issue. Please consider reviewing the associated PR #256.

  4. akaustav commented on Mar 9, 2026

    @akaustav
    ContributorAuthor

    @DinoChiesa / Maintainers - Gentle reminder about this issue. Please consider reviewing the associated PR #256.

  5. akaustav commented on Mar 15, 2026

    @akaustav
    ContributorAuthor

    Attempt number 3 to get the attention of the maintainers / @DinoChiesa to this issue.

  6. akaustav commented on Mar 21, 2026

    @akaustav
    ContributorAuthor

    Attempt number 4 to get the attention of the maintainers / @DinoChiesa to this issue.

  7. akaustav commented on Jun 6, 2026

    @akaustav
    ContributorAuthor

    Attempt number 5 to get the attention of the maintainers / @DinoChiesa to this issue.

  8. akaustav commented on Jul 13, 2026

    @akaustav
    ContributorAuthor

    Attempt number 6 to get the attention of the maintainers / @DinoChiesa to this issue.

  9. akaustav commented on Jul 30, 2026

    @akaustav
    ContributorAuthor

    Thanks to @rakesh-talanki, the fix for this issue has been merged into the master branch of this repository via PR #265. Hence, closing this issue.

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