ASK CHAT GPT: What are the top Application Security and software vulnerability in the CISA KEV catalogue?

CISA KEV CHAT GPT Vulnerability assessment and prioritization in application security

We did ask chatgpt for top application security vulnerabilities observed so far and compared to our data cross-referencing CISA-KEV register to see the top vulnerability exploitable in application security; what we discovered might surprise you.

What are the top vulnerabilities, and what are exploitable? 

Fixing issues immediately is only sometimes possible, and managing the increasing number of vulnerabilities is becoming more challengingFixing issues as soon as they appear is only sometimes feasible and having control over the number of defects generated is becoming increasingly problematic. 

The current state of vulnerabilities is that there are too many vulnerabilities, too little time to solve them, and too few people; some don’t even matter.

In recent research, only a small number of CVEs were exploitable  (10-15%), and the number of vulnerabilities reported yearly is increasing 35% annually.

vulnerability exploitation over time  percentage of vulnerabilities vs total
Exploited Vulnerabilities vs all CVE

Improving Vulnerability remediation with EPSS

vulnerability exploitation over time

Image 1 – CVE Evolution over time

On top of the transformational challenges, we saw an acceleration in the number of CVE declared every year with 2022 having 34% more vulnerabilities declared.  

What are the top Application Security vulnerabilities in CISA KEV?

We were curious to know what was the top vulnerability from an application and software security perspective and asked Chat GPT the question

even though Chat GPT does not have the data on live website information there is a small trick to ask GPT to get acquainted with a website 

can you get acquainted YYY 

Fixing issues immediately is only sometimes possible, and managing the increasing number of vulnerabilities is becoming more challengingFixing issues as soon as they appear is only sometimes feasible and having control over the number of defects generated is becoming increasingly problematic. 

The current state of vulnerabilities is that there are Too many vulnerabilities, too little time to solve them, and too few people, and some don’t even matter.

What are the top exploited vulnerabilities from CISA KEV?

can you get acquainted with https://www.cisa.gov/known-exploited-vulnerabilities-catalog and write the top CISA KEV Vulnerability for software

Yes, I can provide information on the Known Exploited Vulnerabilities (KEV) catalogue and identify the top vulnerability related to CISA-KEV for software.

The KEV Catalog lists known vulnerabilities that cybercriminals have exploited in recent attacks. The CISA KEV catalogue is maintained by the Cybersecurity and Infrastructure Security Agency (CISA), a government agency responsible for cybersecurity and infrastructure security in the United States.

One of the top CISA-KEV vulnerabilities for software listed in the KEV Catalog is the CVE-2019-19781 vulnerability in Citrix Application Delivery Controller (ADC) and Gateway. This vulnerability was first reported in December 2019 and quickly identified as high-risk. It allows an attacker to execute arbitrary code on vulnerable systems, which can lead to a complete compromise of the system.

The CVE-2019-19781 vulnerability was actively exploited by cybercriminals in the wild, leading to numerous successful attacks against organizations that had not yet applied the necessary security patches. In response to the threat, CISA issued an alert in January 2020 urging organizations to apply the necessary security patches as soon as possible.

Since the initial discovery of the CVE-2019-19781 vulnerability, several other vulnerabilities related to CISA-KEV have been identified and added to the KEV Catalog. These include vulnerabilities in software such as Microsoft Windows, Apache Struts, and Adobe products. Cybercriminals have exploited these vulnerabilities in recent attacks, highlighting the need for organizations and individuals to remain vigilant and take proactive steps to protect themselves from these threats.

In conclusion, the CVE-2019-19781 vulnerability in Citrix ADC and Gateway is one of the top CISA-KEV vulnerabilities related to software listed in the KEV Catalog. Organizations and individuals should review the catalog regularly and take the necessary steps to protect themselves from these and other known vulnerabilities that are being actively exploited by cybercriminals. Applying security patches and implementing other security controls can go a long way in mitigating the risk of a cyberattack.

CVE-2019-19781 Vulnerability Timeline:

Application security vulnerability timeline: Starting on January 20, 2020, APT41 used the IP address 66.42.98[.]220 to attempt exploits of Citrix Application Delivery Controller (ADC) and Citrix Gateway devices with CVE-2019-19781 (published December 17, 2019).

Timeline of key events vulnerability in  CVE-2019-19781
Timeline of key events (credit mandiant)

The initial CVE-2019-19781 exploitation activity on January 20 and January 21, 2020, involved the execution of the command ‘file /bin/pwd’, which may have achieved two objectives for APT41. First, it would confirm whether the system was vulnerable and whether the mitigation wasn’t applied. Second, it may return architecture-related information required for APT41 to successfully deploy a backdoor in a follow-up step.  

—-

Exploit Prediction Score / EPSS Analysis :

The information seems to be somehow confirmed by the EPSS ranges

With EPSS data demonstrating that the Citrix Vulnerability is highly exploitable

EPSS cisa kev vulnerability  CVE-2019-19781

The vulnerability resided in the top percentile of exploitability 

EPSS Percentile changes  CVE-2019-19781

What is the KEV Catalog?

The KEV Catalog lists known vulnerabilities that cybercriminals have exploited in recent attacks. CISA, a government agency responsible for cybersecurity and infrastructure security in the United States, maintains the catalogue. The purpose of the catalog is to provide information to organizations and individuals about the vulnerabilities currently being targeted by cybercriminals, so they can take steps to protect themselves from these attacks.

Why is the KEV Catalog important?

The KEV Catalog is important because it helps organizations and individuals to understand which vulnerabilities are most likely to be exploited by cybercriminals. By keeping track of these vulnerabilities, CISA can provide timely alerts and guidance to help organizations and individuals protect themselves from these threats. The catalog is also helpful for security researchers who want to understand the latest tactics and techniques cybercriminals use.

How quickly should you solve it?

In the case of CVE-2019-19781, Citrix released a patch for the vulnerability on January 19, 2020, about a month after the vulnerability was publicly disclosed. However, attackers started exploiting the vulnerability within days of its disclosure, significantly increasing attacks targeting Citrix ADC and Gateway products.

Conclusion

Leveraging a risk-based approach on vulnerability resolutions and correlating all the current data sources available like CISA KEV, EPSS

The Phoenix Security Approach

Phoenix Security Leverage the power of CISA KEV to select and suggest the vulnerabilities that should be fixed automatically.

cisa kev vulnerability in appsec  signal alert phoenix security

Phoenix security takes into account EPSS to calculate the risk exploitation factor.

 

Get in control of your Application Security posture and Vulnerability management

Phoenix security risk vulnerability alerts cisa kev vulnerability in appsec  CVE-2019-19781
cisa kev vulnerability in appsec  CVE-2019-19781

If you want to know more about Phoenix security and doing vulnerability management at scale, contact us https://phoenix.security/request-a-demo/ 

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

The journey of securing an organization’s application landscape varies dramatically, depending on where a company stands in its maturity. Early-stage startups with small security teams face challenges not only with vulnerabilities but also with scaling their security processes in line with their growth. On the flip side, established enterprises struggle with managing complex environments, prioritizing remediation, and dealing with vast amounts of vulnerabilities while staying ahead of sophisticated threats. For startups, the focus is clear—establish visibility and ensure core security practices are in place. Application Security Posture Management (ASPM) tools provide a straightforward, automated approach to detecting vulnerabilities and enforcing policies. These solutions help reduce risk quickly without overburdening small security teams. Mature organizations, on the other hand, are tackling a different set of problems. With the sheer number of vulnerabilities and an increasingly complicated threat landscape, enterprises need to fine-tune their approach. The goal shifts toward intelligent remediation, leveraging real-time threat intelligence and advanced risk prioritization. ASPM tools at this stage do more than just detect vulnerabilities—they provide context, enable proactive decision-making, and streamline the entire remediation process. The emergence of AI-assisted code generation has further complicated security in both environments. These tools, while speeding up development, are often responsible for introducing new vulnerabilities into applications at a faster pace than traditional methods. The challenge is clear: AI-generated code can hide flaws that are difficult to catch in the rush of innovation. Both startups and enterprises need to adjust their security posture to account for these new risks. ASPM platforms, like Phoenix Security, provide automated scanning of code before it hits production, ensuring that flaws don’t make it past the first line of defense. Meanwhile, organizations are also grappling with the backlog crisis in the National Vulnerability Database (NVD). A staggering number of CVEs remain unprocessed, leaving many businesses with limited data on which to base their patching decisions. While these delays leave companies vulnerable, Phoenix Security steps in by cross-referencing CVE data with known exploits and live threat intelligence, helping organizations stay ahead despite the lag in official vulnerability reporting. Whether just starting their security program or managing a complex infrastructure, organizations need a toolset that adapts with them. Phoenix Security enables businesses of any size to prioritize vulnerabilities based on actual risk, not just theoretical impact, helping security teams navigate the evolving threat landscape with speed and accuracy.
Francesco Cipollone
The cybersecurity world is reeling as MITRE’s funding for the CVE and NVD systems expires, disrupting the backbone of global vulnerability management. As traditional sources like the National Vulnerability Database collapse under funding cuts and submission backlogs, security teams face delays, incomplete data, and loss of automation in remediation pipelines. This isn’t just a data problem—it’s a structural crisis for application security and vulnerability correlation. In this landscape of uncertainty, Phoenix Security’s ASPM platform steps up with a code-to-cloud correlation engine that doesn’t depend on outdated data workflows. By connecting code-level insights (including tools like Semgrep) to runtime and cloud environments, Phoenix enables faster, context-aware vulnerability remediation—even as NVD and CVE pipelines deteriorate. This article dives into the implications of the CVE shutdown and how Phoenix Security is helping security and development teams transition to a resilient, correlation-first approach to cybersecurity.
Francesco Cipollone
Learn how to predict ransomware risks and vulnerability exploitation using a threat-centric approach. Explore data-driven insights, verified exploit trends, and methods for assessing the likelihood of attacks with key references to CISA KEV, EPSS, and Phoenix Security’s 4D Risk Formula.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
The recent Google acquisition of Wiz for $32 billion has sent shockwaves through the cybersecurity industry, particularly in the realm of Application Security Posture Management (ASPM). This monumental deal highlights the critical importance of cloud security and the growing demand for robust ASPM solutions. While the acquisition promises potential benefits for Google Cloud users, it also raises concerns about vendor lock-in and the future of cloud-agnostic security. Explore the implications of this acquisition and discover how neutral ASPM solutions like Phoenix Security can bridge the gap in multi-cloud environments, ensuring continuous, collaborative, and comprehensive security from code to cloud.” – Find Assets/Vulns by Scanner – Detailed findings Location information Risk-based Posture Management – Risk and Risk Magnitude for Assets – Filter assets and vulnerabilities by source scanner Integrations – BurpSuite XML Import – Assessment Import API Other Improvements – Improved multi-selection in filters – New CVSS Score column in Vulnerabilities
Alfonso Eusebio
x  Powerful Protection for WordPress, from Shield Security
This Site Is Protected By
ShieldPRO