Python Import as an Execution Boundary: An Empirical Study of Bugs, Vulnerabilities, and Analysis Gaps

arXiv:2609.14791 · cs.CR · Submitted 2026-09-13 · Read on arXiv

cs.CR

Submitted: 2026-09-13

Updated: 2026-09-13

Code: https://github.com/awen-li/ImportMine

Project page: https://microsoft.github.io/pyright/#/configuration?id=

License: http://arxiv.org/licenses/nonexclusive-distrib/1.0/

Terminology

• Benchmark — 7× in this paper · explained in 2 episodes
• Trace — 6× in this paper · explained in 2 episodes
• Core — 4× in this paper · explained in 2 episodes
• Verification — 3× in this paper · explained in 2 episodes
• Consistency — 1× in this paper · explained in 3 episodes

Sources

• Scalpel: The Python Static Analysis Framework
• A Large-Scale Security-Oriented Static Analysis of Python Packages in PyPI

Related papers

• SoK: AI-Augmented Binary Reversing
• Relaxed Sender Anonymity for CBDC Interbank Settlement: A Zero-Knowledge Approach on Permissioned EVM
• Calibration-Family Overfit: Why Trusted Sabotage Monitors Don't Transfer Across Lineages
• Efficient Fuzzy PSI under One-Sided Assumptions
• Sealing the Audit-Runtime Gap for LLM Skills
• Token Composition: A Graph Based on EVM Logs