Papers for

application developers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Vulnerability detection improves with structured code behavior explanations

Structured Security Explanations for Learning-Based Vulnerability Detection

Abstract: Software vulnerability detection remains difficult because existing approaches rely on predefined analysis rules, learn vulnerability patterns implicitly from code and labels, or use large language models (LLMs) to make the final security judgment. It remains unclear whether structured descriptions of security-relevant program behavior can improve supervised detection. We present VulnLens, an explanation-augmented framework for binary C/C++ vulnerability detection that separates program-behavior analysis from the final decision. A label-blind LLM-based Explainer examines each function from seven fixed perspectives: data flow, memory access, object lifetime, arithmetic and type behavior, control flow, shared state, and external-resource access. Without receiving vulnerability labels or CWE information, it generates structured explanations. A supervised Detector combines source code and explanations through sequential cross-attention. We evaluate VulnLens on a PrimeVul-derived dataset covering ten CWE categories and test transfer to SecVulEval without retraining. On the 526-function PrimeVul test set, VulnLens achieves 75.5% accuracy and 77.2% F1, exceeding DeepSeek V4 Pro by 4.2 percentage points in accuracy and Gemini 2.5 Pro by 2.2 points in F1. Matched explanations improve F1 by 7.3 points over a separately trained code-only detector. On SecVulEval, VulnLens achieves 66.4% accuracy and 65.8% F1, outperforming DeepSeek V4 Pro by 7.6 points in accuracy and 20.0 points in F1, and Gemini 2.5 Pro by 16.6 points in accuracy and 7.8 points in F1.

Tue 27 OctCryptography and SecuritySoftware Engineering
The gist
Detecting security problems in software is hard because current tools either rely on fixed rules or try to learn patterns from large code samples without clear reasoning. The authors developed VulnLens, which first explains what a piece of code does in a structured way, then uses that explanation to help detect vulnerabilities. This approach works better than previous methods, particularly when tested on different sets of code without retraining. It shows that clear descriptions of code behavior can boost accuracy in spotting security issues.
Open → 2610.37797v1

Coding agents tested with dynamic multi-turn user simulations

SWE-DIVE: Multi-Turn Coding Agent Evaluation with Dynamic User Simulation

Abstract: Coding agents are typically evaluated using one-shot, well-formulated prompts. Benchmarks such as SWE-bench use existing GitHub issues as input for a coding agent and evaluate whether the agent successfully solves the task. However, in real-world use cases, prompts are often not as well-formulated or structured as existing GitHub issues. Additionally, a coding agent session is not limited to a single prompt; it typically involves a multi-turn interaction in which the user iteratively adds new tasks and requirements that the agent must fulfill. To benchmark these abilities, we developed SWE-DIVE, a dynamic, interactive validation and evaluation framework for benchmarking coding agents in a multi-turn environment. To achieve this, we introduce a user simulator that can simulate different behavioral patterns and communicate with the coding agent. We also introduce a conversation validator that evaluates the user simulator's outputs to determine whether they fulfill the initial requirements and guide the agent toward successfully solving the task. The entire framework is embedded in a Harbor environment, which orchestrates the coding agent, user simulator, and conversation validator, and executes the test environment to determine whether the agent successfully solves the task. Our results and source code are available in our GitHub repository (https://github.com/lorenzbrehme/swe-dive_usersim).

Wed 21 OctSoftware EngineeringArtificial Intelligence
The gist
Typical testing for coding assistants uses single, clear questions, but real users ask many questions one after another, adding new details each time. The authors created SWE-DIVE, a system that acts like a user having a back-and-forth chat with a coding assistant to better test how well the assistant works in real-life conversations. This system also checks if the assistant solves the task correctly by following the evolving requirements. This approach helps to evaluate coding agents in a more realistic and interactive way.
Open → 2610.30047v1

Coordinating diverse AI models for efficient joint task solving

Toward Collective Model Intelligence: Characterizing and Coordinating Models

Abstract: Independently developed AI models accumulate diverse and complementary capabilities, but a growing model collection does not automatically realize Collective AI. Addressing this gap requires understanding model capabilities with limited evaluation, organizing complementary models to collaborate on diverse tasks, and executing model calls efficiently under resource constraints. We present a systematic approach to pursuing Collective Model Intelligence through three connected components. First, Model Eval constructs evidence-based capability profiles by combining query-level performance estimation with cross-domain prediction, reducing the need for exhaustive evaluation. Second, Mio (Models in One) organizes complementary model candidates and supports task-conditioned, cost-aware selection and collaboration as task requirements evolve. Third, Mos (Model Serving OS) separates model selection from execution and provides endpoint scheduling and shared model deployment and distribution. Experiments show lower capability-estimation errors under limited evaluation. Across nine public benchmarks, Mio 1.0 Lite achieves the highest average score and lowest average cost among compared methods, with per-request costs 73.7-97.5% lower than those of the best-scoring alternatives. A prewarmed shared cache accelerates model-file retrieval by up to 23.3 times. This work lays a foundation for Collective Model Intelligence by characterizing and coordinating the diverse capabilities of an expanding model universe.

Sat 17 OctArtificial Intelligence
The gist
As more AI models are created independently, they each have their own strengths and weaknesses. The paper presents ways to understand what each model can do without testing everything, and how to pick and combine models to work together on different tasks efficiently. They also built a system to handle running these models in a smart way to save time and resources. This approach showed it could better estimate model skills and do tasks more cheaply and quickly than other methods they compared it to.
Open → 2610.24739v1

Security risks found in software using judgment models to guide decisions

Nudge the Judge: Uncovering Program Decision Hijacking in Real-World Jev Applications

Abstract: System One models such as Jev change how software makes decisions by mapping open-ended semantic contexts into structured judgments that directly drive program execution. However, this paradigm introduces a new security risk, which we term Jev Program Decision Hijacking (JPDH): attacker-controlled contexts can redirect program decisions through schema-valid Jev judgments. Existing evaluations focus primarily on model-level attacks or predefined injection channels, leaving attack reachability and downstream security consequences in real-world Jev applications underexplored. In this paper, we present JevProbe, the first automated framework to evaluate JPDH by tracing adversarial influence from reachable context surfaces through program-consumed decisions to downstream security consequences in real-world Jev applications. Our key insight is that application logic maps diverse Jev judgments to observable decisions, enabling systematic, program-grounded attack evaluation. Across 228 popular real-world Jev applications and 2,273 test cases, 81.5% exhibit decision flips, of which 98.6% lead to potential downstream security impacts. Compared with the strongest adapted baseline, JevProbe improves macro-average Decision Flip Rate (DFR) by 50.4 percentage points, while existing defenses offer limited protection. We further construct JevProbeBench to support systematic evaluation of JPDH in real-world Jev applications. We have responsibly disclosed our findings to Jev application maintainers, pending their responses. The source code of JevProbe and the JevProbeBench dataset are publicly available on GitHub (https://github.com/xiaoxiaohg8d/JevProbe-).

Tue 13 OctCryptography and SecurityArtificial Intelligence
The gist
Software that uses special models called Jev models makes decisions by turning open-ended information into clear choices that affect how the software works. The authors found a new kind of security risk where attackers can trick these systems using valid but manipulated judgments, causing the software to behave wrongly. They created a tool named JevProbe that can automatically find these vulnerabilities by following how the software uses these judgments in real programs. They tested many real applications and discovered that most are vulnerable to manipulated decisions that may cause security problems.
Open → 2610.18612v1

System One model adapters can change final decisions unexpectedly

DICE: Tilting the Odds through Interface Attackson System One Model

Abstract: System One models offer typed judgments that applications can turn into decisions. Their answers, however, are conditional on the state and question supplied by surrounding components, and on how the application uses the response. We study this boundary in a Jev-based pipeline with bounded substitutions at three adapter outputs: state extraction, question generation, and output interpretation. Across three small synthetic studies, each adapter can change the final decision while Jev and its authentic API responses remain outside attacker control. The cases expose distinct failures of source fidelity, answer meaning, and response relevance. Checks that bind these relationships stopped the corresponding interventions we tested, although source verification also rejected some valid clean decisions. The pilot identifies where correct request-level judgments can lose their connection to the original task; it does not estimate the prevalence of these failures in deployed systems.

Fri 9 OctCryptography and SecuritySoftware Engineering
The gist
System One models give answers based on the information they receive, but how other parts of an application handle those answers can change the final decision. The authors studied how three different points—taking data, asking questions, and interpreting answers—can be altered to shift decisions, even though the core model and its real outputs can’t be controlled by an attacker. They found different ways the connection between what the model means and what the application does can break down. Some checks helped stop these changes but also sometimes blocked good decisions.
Open → 2610.14404v1

Jev decision layer exposes security and privacy vulnerabilities

Hidden Risks of Jev: An Empirical Study of Security, Privacy, and Dual Use

Abstract: Jev turns natural-language questions into typed answers and probabilities with low latency and cost, enabling applications to route requests and select tools. While this interface allows Jev to integrate naturally into application workflows as a decision layer, the security and privacy implications of this emerging use remain largely unexplored. To address this gap, we conduct the first systematic study of these implications using the official Jev API and NanoJev, a local model with controllable training data and updates, focusing on three research questions: (1) What security threats arise when Jev is deployed as an application decision layer? (2) What private information can Jev reveal despite returning constrained typed outputs? (3) How can Jev's general-purpose decision capability be used for beneficial purposes or misused? Jev's decisions depend on application state and may be influenced by user-provided inputs. We therefore adapt prompt injection and adversarial suffixes to manipulate its decisions. Open-source Jev distribution and updates introduce supply-chain risks, which we examine by implanting backdoors in NanoJev through training data poisoning. Since Jev's outputs reflect both application state and information learned during training, we further adapt membership, private attribute, and internal knowledge inference attacks to recover sensitive information despite its constrained output format. Finally, Jev can serve as a general-purpose decision oracle for defensive and malicious workflows. We examine this dual use through four detection tasks covering prompt injection, jailbreak inputs, harmful content, and AI-generated text, alongside misuse scenarios involving jailbreak and model extraction. Our empirical evaluation shows that Jev remains vulnerable to the examined security and privacy threats, while its decision capability can support beneficial and malicious uses.

Sun 4 OctCryptography and SecurityArtificial Intelligence
The gist
Jev is a tool that answers questions quickly and cheaply, helping apps make decisions. The authors studied whether using Jev in apps could cause security or privacy problems. They found Jev can be tricked into making wrong decisions and might reveal secret information. They also showed Jev can be used for both helpful tasks and potential misuse. This study highlights risks and benefits of using Jev as a decision-making tool.
Open → 2610.04985v1

Agent performance depends on both language model and harness used

Finding the Right Fit: Model-Harness Interactions across Agent Tasks

Abstract: Choosing an agent system means choosing both a language model and the harness through which it acts. We ask whether a strong model, harness, or pairing stays strong when the setting changes. We evaluate 66 configurations: four configurable harnesses (OpenHands, DeepSeek Harness, PI, and openJiuwen) paired with five models on TUA-Bench, ALE-CLI, and Terminal-Bench 4, plus the native Codex-GPT and Claude Code-Claude pairings. Model rankings reverse across harnesses. On Terminal-Bench 4, Claude leads GPT by 7.94 points in OpenHands but trails it by 30.16 points in PI. For four of the five models, the best harness changes from one benchmark to another, yet some pairings hold: openJiuwen gives Kimi its highest score on all three benchmarks, by 5.61 to 11.11 points. A model's own vendor harness is not reliably its best, and higher cost does not reliably buy a higher score. On Terminal-Bench 4, GPT scores higher under PI than under DSH at less than a quarter of the cost per task. Matched trajectories suggest why fit varies. Models start almost all repairs themselves, so much depends on whether the harness hands failures back in a form the model can use. GPT does best with PI's lean scaffold, while Kimi, which often issues malformed tool calls, does best in openJiuwen. We argue that the model, the harness, and the task should be evaluated together, and we release the harness adapters, evaluation code, and all 6,204 scored trajectories at https://github.com/liyix/finding-the-right-fit and https://huggingface.co/datasets/yixuanli97/finding-the-right-fit.

Thu 1 OctArtificial IntelligenceSoftware Engineering
The gist
Choosing how to run an AI agent means selecting both the language model and the system that controls it, called a harness. The authors found that the best model doesn't always do best with every harness, and the best pair changes depending on the tasks. They showed that some models work better with simpler harnesses, while others need more error-tolerant systems. Their work suggests that agents should be tested as a combination of model, harness, and task to find the best fit.
Open → 2610.00917v1

Vision language models reuse reading parts to specialize in OCR tasks

From Retrieval to Recognition:How Vision--Language Models Become OCR Specialists

Abstract: Does a general vision--language model acquire specialized OCR ability by developing a new reading circuit or by reusing an existing mechanism? We address this question in the setting of full-sequence OCR, rather than local-answer retrieval. Using an evidence-grounded protocol with held-out causal interventions, we identify sparse and stable OCR-head sets in GLM-OCR, MinerU2.5, and PaddleOCR-VL-1.6. We then investigate the mechanistic origin of these OCR heads by comparing them with independently identified textual retrieval/copy heads in general VLMs. Across two general VLMs, visual OCR heads strongly overlap independently identified textual retrieval/copy heads, yielding untuned top-20 intersections of 73.3% and all-head Spearman correlations of 0.677-0.886. The overlap and causal interventions suggest that full-sequence OCR operates as dense sequential multimodal copy-and-paste, repeatedly retrieving visual evidence and routing it to the current output position. Finally, we examine how this shared circuit changes as a general VLM becomes an OCR specialist. Matched base-to-specialized comparisons show that OCR specialization largely preserves head identity, retaining 17-20 of the top 20 heads per task with all-head rank correlations of 0.874-0.942, while redistributing their functional and causal strengths.

Fri 18 SeptComputer Vision and Pattern Recognition
The gist
Reading text in images is a tricky task for computers, and it wasn’t clear if general vision language models had to build new special parts to get good at it. The authors found that these models actually reuse certain components made for copying and retrieving text to become experts at OCR, which is reading out full text sequences. They also saw that as the models specialize, they keep the same parts but change how strong or important each part is for reading. This means OCR in such models works like repeatedly copying visual clues and pasting them in the right order.
Open → 2609.21543v1