Skip to content
Introducing Auri Fix For Open Source

Introducing Auri Fix For Open Source

www.endorlabs.com • October 27, 2026

Our research found only 10% of reachable open source findings in enterprise codebases could be fixed with a straightforward upgrade, while 82% had a remediation option in first-party code.

Frontier AI models are discovering and exploiting security vulnerabilities faster than enterprises can fix them. Last week showed what vulnerability response looks like now: multiple urgent CVEs and patches landing at once, competing for the same engineering time.

On Oct. 21, PHP shipped emergency patches for two critical remote code execution (RCE) flaws found with an OpenAI model, and governments from Germany to Japan took public websites offline rather than run unpatched code. In the same few days, GitLab and Node.js released fixes for critical RCE vulnerabilities, and Node.js and Go shipped releases to deal with a compromised intermediate certificate authority .

Weeks like that are becoming routine. Earlier this year, J.P. Morgan reported that vulnerability discovery is outpacing remediation by 16.5x , and Bank of America CEO Brian Moynihan recently told CNBC the bank added 1,000 contractors to its 3,000 employees this year to patch vulnerabilities uncovered by Mythos.

With few options, leaders are left trying to brute force a solution. When exploits can be built in hours , waiting for an upstream release is too slow, upgrading can break the build, and forking a dependency leaves your team maintaining code it didn’t write, forever, or paying a vendor to do it for you.

Today, we’re introducing AURI Fix for Open Source , part of AURI by Endor Labs. It assesses reachability and exploitability in the context of your application, then recommends the fix with the least effort, disruption, and maintenance:

Upgrade the dependency to a version that fixes the vulnerability.

Mitigate in code by changing how your application uses the dependency.

Patch the dependency with a targeted security fix.

Replace the dependency with an alternative, or remove the functionality that requires it.

New in this release, AURI can mitigate vulnerabilities in application code or configuration, typically in fewer than 10 lines. The change breaks the exploit path and leaves the vulnerable dependency in place, so teams can close exposure in minutes in code they already know and maintain without waiting for an upstream patch or maintaining a fork.

Use reachability to identify where to act

An application’s exposure depends on how it uses a vulnerable dependency. The inputs it passes, the APIs it calls, and the features it enables can determine whether a vulnerability is exploitable.

That creates another place to intervene. A targeted change to your application can block an exploitable path while your team plans a broader dependency upgrade. That might mean restricting an input before it reaches a vulnerable function or changing a configuration setting that exposes unnecessary functionality.

Our research into buffa, a Rust Protocol Buffers library maintained by Anthropic, provides a concrete example. Endor Labs AI SAST flagged an allocation flow from untrusted input. Further investigation uncovered a memory-amplification vulnerability, now tracked as CVE-2026-55407 , that could exhaust a service’s memory.

Upgrading fixed the dependency. Teams unable to upgrade immediately also had an application-side option : regenerate their code with unknown-field preservation disabled, removing the retention behavior that fed the vulnerable allocation. Whether that mitigation was appropriate depended on the application’s need to preserve those fields.

Select the fastest, safest fix automatically

AURI Fix brings that decision into the remediation workflow. It evaluates how your application uses a vulnerable dependency to recommend an upgrade, a code mitigation, a dependency patch, or a replacement:

Is it reachable and exploitable? AURI checks reachability, exploitability, severity, and deployment context. If no, accept and document the risk.

Can you upgrade without breaking? AURI finds the minimum safe upgrade. If yes, it applies the upgrade by opening a pull request.

Is it a configuration gap, not vulnerable code? Some CVEs only apply under a specific setting. If yes, AURI makes a local config change. ( New in this launch)

Is the exposure in how you use the library? The vulnerable path runs through your own code. If yes, AURI applies a mitigation in your own code. ( New in this launch)

Is the upgrade blocked or unpatched upstream? Pinned versions, breaking APIs, or no fix yet. If yes, apply a backported patch, a zero-day patch, or fork and vendor.

Is the dependency itself the liability? Unmaintained, a repeat offender, or barely used. If yes, use Endor Scores to swap in an alternative, or rewrite and remove it.

82% of reachable OSS findings can be mitigated in first-party code

Our research team analyzed 264,643 reachable findings in enterprise codebases across cybersecurity, financial services, insurance, and software companies. In that analysis, 82% of reachable findings in direct and transitive dependencies had a first-party remediation option. Only 10% could be addressed through a straightforward upgrade without substantial refactoring and testing.

These findings describe the availability of remediation options. They show how often an application-side intervention may be possible when upgrading is difficult or an upstream fix is unavailable.

Two approaches accounted for more than half of the findings studied: controlling inputs at the call site, at 35.9%, and changing a configuration flag, at 21.3%. Those are the focus of this release.

Most changes are small. In testing, the median pull request was 6 lines , in code developers already review and maintain, with a median cost of $0.018 per fix .

Not every fix is a code change. Some vulnerabilities only apply under a specific setting, and the safest interim fix is switching that setting off. Last week’s PHP flaws were an extreme case: the bug sat in PHP’s C runtime, below any application code, and exposure depended on how the runtime and endpoints were configured. AURI Fix applies the same reasoning to open source dependencies.

In the example below, a Java application reaches a denial-of-service vulnerability in Spring Boot Actuator ( CVE-2023-34055 ), but none of its own code is on the path. Spring Boot calls the vulnerable function through a metrics filter it installs automatically. AURI Fix finds the one property that turns that path off, sets it, re-evaluates the configuration to confirm no path remains, and opens a pull request that explains the tradeoff: the application stops recording one request metric, and upgrading remains the complete fix.

The flow is triggered directly from the Endor Labs CLI using endorctl fix:

Teams can put fixes into production in two ways:

Policy-based workflows: The Endor Labs policy engine opens a pull request with the proposed fix (shown above). Your team reviews it, runs tests, merges, and deploys.

Agentic remediation workflows: An AURI agent triages which findings to fix first, chooses the remediation method, applies the fix, and opens the pull request. Your team approves the merge.

Verified evidence for compliance reporting

Alongside each fix, AURI Fix generates a VEX report that records why the vulnerability is no longer exploitable, so downstream scanners and security teams can suppress the finding based on evidence. This is important because a first-party mitigation leaves the vulnerable dependency version in place, so any other scanner that inspects your software will keep flagging it.

This matters most for software vendors whose products get scanned again inside their own customers’ environments, where an unexplained finding turns into a support ticket or a blocked deployment. Under mandates like the CRA, that evidence carries more weight. A vendor facing a 24-hour reporting window needs to know, and show, which flagged components are actually exploitable.

Our goal is to shorten the time between identifying an exploitable vulnerability and addressing it in production. AURI Fix gives teams more ways to act, grounded in how their applications use open source dependencies.

AURI Fix for Open Source is available now in private beta. us or reach out to your Endor Labs account team to try it.

When you're ready to take the step in securing your software supply chain, here are 3 ways Endor Labs can help:

See the four levels live

Join Robert Haynes, author of the playbook, for a live walkthrough of all four levels: live demos, straight answers on build vs. buy, and time for your questions.

Extracted Entities