paper-with-me

Papers

MPC-Patch-Bench: Security-Aware LLM Code Patch for Multi-Party Computation

2026-06-09 · Yukuan Zhang, Mengxin Zheng, Qian Lou arxiv

Repository-level benchmarks for evaluating Large Language Model (LLM) code repair on Secure Multi-Party Computation (MPC) software do not yet exist, and directly transplanting general-purpose benchmarks such as SWE-bench fails on three structural fronts: (i) MPC repositories are dominated by generic Python infrastructure rather than cryptographic logic; (ii) high-value MPC fixes lack the standardized tests rigid extraction pipelines require; and (iii) standard fail-to-pass evaluation is insufficient for code that must also be cryptographically safe. MPC is increasingly deployed for privacy-preserving machine learning, biomedical collaboration, and secure analytics. Existing MPC-specific code-synthesis efforts cover only operator-level or single-framework tasks; evaluating LLM agents on real repository-level MPC repair instead demands MPC-aware data curation and a verifier matched to the security and numerical-fidelity guarantees MPC programs must obey neither of which existing benchmarks provide. We introduce MPC-Patch-Bench, a repository-level benchmark organised around two frameworks. (1)The Data Curation Framework combines a domain-specific curation agent that filters raw pull requests through three cryptographic layers with a human-AI completion engine that synthesizes missing problem statements and Fail-to-Pass/Pass-to-Pass tests, yielding 205 fully verified instances. (2)The MPC Verifier provides dedicated security and numerical-fidelity checks via dynamic differential testing against plaintext oracles and MPC-specific static analysis rules that flag unsafe reveals, insecure arithmetic, and illegal public/private casts. The strongest evaluated LLM functionally resolves only 22.9% of MPC-Patch-Bench tasks; the MPC Verifier further reduces verified resolution to 17.1%, with up to 40% of functionally-passing patches rejected for cryptographic or numerical-fidelity violations.

📄 PDF Abstract BibTeX arXiv:2606.11416

Code (0)

등록된 구현이 없습니다.

Tasks

Code Repair

Similar Papers 제목 키워드 기반

Repository-Level Graph Representation Learning for Enhanced Security Patch Detection

2024-12-11 · Xin-Cheng Wen, Zirui Lin, Cuiyun Gao, Hongyu Zhang 외

Software vendors often silently release security patches without providing sufficient advisories (e.g., Common Vulnerabilities and Exposures) or delayed updates via resources (e.g., National Vulnerability Database). Ther…

graph constructionGraph Representation LearningRepresentation Learning

Detecting Security Patches via Behavioral Data in Code Repositories

2023-02-04 · Nitzan Farhi, Noam Koenigstein, Yuval Shavitt

The absolute majority of software today is developed collaboratively using collaborative version control tools such as Git. It is a common practice that once a vulnerability is detected and fixed, the developers behind t…

Time Series

Just-in-Time Detection of Silent Security Patches

2023-12-02 · Xunzhu Tang, Zhenghan Chen, Kisub Kim, Haoye Tian 외

Open-source code is pervasive. In this setting, embedded vulnerabilities are spreading to downstream software at an alarming rate. While such vulnerabilities are generally identified and addressed rapidly, inconsistent m…

Contrastive LearningData AugmentationRepresentation Learning

Why LLMs Fail: A Failure Analysis and Partial Success Measurement for Automated Security Patch Generation

2026-03-10 · Amir Al-Maamari arxiv

Large Language Models (LLMs) show promise for Automated Program Repair (APR), yet their effectiveness on security vulnerabilities remains poorly characterized. This study analyzes 319 LLM-generated security patchesacross…

Program Repair

BackportBench: A Multilingual Benchmark for Automated Backporting of Patches

2025-12-01 · Zhiqing Zhong, Jiaming Huang, Pinjia He arxiv

Many modern software projects evolve rapidly to incorporate new features and security patches. It is important for users to update their dependencies to safer versions, but many still use older, vulnerable package versio…