> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/changelog/version-5.17-june-2025.md).

# Version 5.17 - June 5, 2025

Version 5.17 introduces key upgrades to enhance usability for drill down and malware identification, extend static analysis, and improve performance to reduce time and minimize impact on DevOps and developer workflows. This release focuses on making vulnerability management more seamless, expanding language coverage, and accelerating secure development processes.

### 🧩 Improved Navigation Experience

We’ve redesigned how users interact with risks and assets across the platform.

* **All Risks** is now the single entry point for all findings—navigate between SAST, SCA, Secrets, IaC, and Build risks via tabs without leaving the section
* New **switch buttons** allow fast toggling between risks and assets views—move instantly from vulnerabilities to components or projects

This simplified navigation improves visibility, reduces context switching, and enables faster triage and issue resolution.

<figure><img src="/files/uo5ZpKen629sSdEHNAnZ" alt=""><figcaption></figcaption></figure>

### ☠️ Malware Directly Integrated into Products

Malware findings are now visible directly within their respective product sections.

* Reverse shells flagged under **CI/CD**
* Malicious components exposed in **SCA**
* Potential malware in application code detected through **SAST**
* All malware issues marked with **maximum severity** and a **skull icon** for immediate visibility

This ensures critical threats are impossible to overlook and are prioritized as part of normal workflows without extra steps.

<figure><img src="/files/k7j2zuO3eS7NAK5wuKdH" alt=""><figcaption></figcaption></figure>

### 🐍 Python Support in SAST

Our proprietary static analysis engine now provides full support for **Python**.

* Coverage extended to modern frameworks and coding patterns
* Analysis tailored to detect the most relevant vulnerabilities in Python projects

With this, teams can confidently secure Python codebases alongside other supported languages, broadening static security coverage

<figure><img src="/files/2VqLtQuo0Wv9te31zAQo" alt=""><figcaption></figcaption></figure>

### 🚀 SAST Engine Performance Boost

We’ve enhanced our SAST engine to deliver **20% faster scan times** on average.

* Reduced overhead during scans without sacrificing depth or accuracy
* Minimized disruption to CI/CD pipelines and developer workflows

Faster analysis cycles enable quicker feedback and help maintain high development velocity while strengthening security posture.

### 🤖 AI Auto-Fix for SAST (Beta)

We’re launching beta access to AI-powered auto-fix for SAST.

* Automatically **suggests and applies secure code fixes**
* Reduces the burden on developers and **accelerates remediation** efforts

This capability helps teams focus on secure delivering of new features with high value and high-quality for the business.

<figure><img src="/files/KOiXgYGdUnadWncjDSxt" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xygeni.io/changelog/version-5.17-june-2025.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
