Intel

AIKIDO-2026-712855

graphifyy is vulnerable to Information Disclosure

Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Jul 17, 2026
July 17, 2026

53

CVE Score

Medium

Information Disclosure

Are you affected? Scan for Free

TL;DR

The graphify code-graph extractor derives node IDs and source_file values from filesystem paths when it builds a committed graph.json. For reference targets outside the scan root and for degenerate symbol or config-key names (such as a minified $ or a JSONC "//" key) that normalize to nothing, the ID derivation falls back to the absolute scan path, embedding it, including the local OS username and home directory, into the graph artifact. Anyone who reads a shared or published graph.json can then recover the local username and directory layout of the machine that generated it. The fix rewrites out-of-root targets to a portable ext_ id with a walk-up source_file and skips degenerate names so no absolute path is written into node IDs or source_file.

How do I fix this?

Upgrade the graphifyy library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Package

Versions

0.8.19 - 0.9.15

Fixed in 0.9.16

Background info

graphifyy is vulnerable to Information Disclosure in versions 0.8.19 - 0.9.15.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea