
Release Notes · Enterprise Server 6.2 · November 2026
In 6.1, Pixee started looking for vulnerabilities on its own, planning each search from the repository's threat model. 6.2 turns to the rest of your program. If you run Checkmarx Enterprise or Polaris, their findings now come into Pixee natively. If your repositories belong to different teams, fix feedback can now follow those teams.
The vulnerability search that started in 6.1 is now Pixee Beacon, and it reads your code the way an attacker would. It works out what each repository protects and who can reach it, has a verifier try to disprove leads by reading the code, and sends what's left through Pixee's triage before any fix is written. Each run ends by telling you what it examined, what it found and what it ruled out. To see how Pixee searches for vulnerabilities, start at the Pixee Beacon page.
• Findings from more of your tools. Checkmarx Enterprise (CxSAST), native Polaris, Azure DevOps through a VM managed identity, and a Sonar project picker.
• Projects. Group repositories by team and leave fix feedback that applies to the whole group.
• Triage and fixes. Reachability for each dependency chain, and a fix planner that keeps your declared dependency versions.
• For the team that runs Pixee. An external database for every component, admin-only control over integrations and workflows when role-based access is enforced, and service accounts under role-based access.
• Pixee Beacon. Pixee's own search for vulnerabilities, planned from each repository's threat model, with its findings in the same triage and fix queue as your scanners'.
Your scanners stay the main feed for Pixee, and 6.2 connects more of them.
• Checkmarx Enterprise (CxSAST). Upload results, or pull findings from a live CxSAST server, from the create-scan flow.
• Polaris. Pixee pulls findings from the Polaris Findings API, imports Polaris SCA and maps repositories to Polaris projects. For Azure DevOps repositories you opt in, it creates Polaris scans when a build completes.
• Azure DevOps. Connect with a VM managed identity instead of a stored token.
• Sonar. Search for the Sonar project when you bind a repository, instead of typing its key.
• Integration settings. Integrations is now the first tab in organization settings. Each instance lists the repositories that use it, and a repository shows when no instance is bound for a tool. Bitbucket and Azure pickers are now typeaheads.
Admins can now group repositories into projects, for example one per product team. When you leave feedback on a fix, you can scope it to the project, and it applies to every repository in it.
One behavior change comes with this. Feedback on fixes used to apply across your whole deployment. From 6.2 it applies to the repository where you left it, so guidance you want more widely should be left again at project level.
• Reachability per chain. The SCA dependency graph gives a reachability verdict for each chain that pulls in a vulnerable package, and highlights the path.
• Fixes keep your versions. The SAST fix planner is now instructed never to change a declared dependency version, and SAST fixes no longer edit lockfiles. Fixes also include the test-file changes they planned.
• CVSS v4 first. Dependabot findings use the CVSS v4 score when one exists.
• Scans that finish. One malformed SARIF result no longer fails the whole scan. An analysis that fails before it starts is queued again, and the retry reuses the code already uploaded. AppScan RapidFix analyses keep running until they finish, and Pixee checks that the results reach AppScan.
• Findings views. Each repository's findings get a resolution panel and a branch selector, dashboard filters apply to every chart, and quick-view totals count only findings analyzed end to end. Pixee Overview KPIs count each finding once, even when several scans report it. Uninstalled GitHub repositories drop out of the repository list by default, and a threat-model refresh that stalls now says why.
All of this feeds the same triage and fix loop as before. For the findings your scanners send, Pixee's 2025 customer cohort reached a 94% end-to-end resolution rate, from scanner finding to handled decision.
• External databases. Every component can use an external database.
• Role-based control. With role-based access control enforced, only admins can change integrations, coding guidelines and workflows. Service accounts can mint platform tokens under role-based access. A Pixee CLI login left unused for 24 hours has to sign in again.
• Operations. The Cluster Console sits behind the Gateway, support bundles carry a capacity snapshot, and an alert fires when an analysis fails because it couldn't start in time.
We also kept hardening Pixee itself in this release.
Beacon starts from the repository's threat model, which names the trust zones, the sensitive assets, the security controls and the dangerous calls. It maps the repository's entry points and what they let a caller do, then follows attack paths into the code, from inputs toward dangerous calls and from dangerous calls back to whoever can reach them.
Candidates go to a verifier, up to a per-run limit, that tries to disprove each one by reading the code. What the verifier can't refute, and anything past the limit, goes to Pixee's triage, and what survives gets the same fix pull requests as any scanner's findings. Beacon uses rules only to find the risky calls an investigation starts from, so your scanners stay the main feed.
In one of our own runs, at Medium effort on a test copy of the open-source Umbraco CMS, the verdict read "Beacon examined 44% of Umbraco-CMS's attack surface." The badge said Gaps, and each gap named a cause and a next step, such as rescanning at High effort when the token budget ran out. The leads the verifier or triage ruled out stayed on the page with the reasoning.
The Pixee Beacon page shows more real runs on open-source code, with their threat models, dismissed leads and coverage verdicts.
All of it, from the Checkmarx and Polaris connections to Projects and Beacon, is in the latest 6.2 release.
Every Thursday, 1,500+ security leaders get the week in AppSec cut down to a 5-minute read.
Join 1,500+ security leaders. Five minutes, once a week.
Your first issue lands Thursday.
One email a week. Unsubscribe in one click.