Issue 13 · Nov 2–8, 2026Editions · Glossary · Archive · Method · RSS · HU / ENG

News of the AI era, curated weekly

Glossary › Security

vulnerability

basicwidespread

A vulnerability is a flaw or weak point in software, a device or an AI system that an attacker can exploit to do something they are not authorized to do.

In plain terms

Imagine you have a window in your apartment with a faulty lock. As long as no one notices, nothing happens, but the possibility exists: whoever knows about it can enter through it. A vulnerability is exactly such a poorly locking window in a program, phone, website, or AI system.

A vulnerability is not an attack or damage in itself, only the possibility of one. It is important to know about it because if found and fixed before a malicious actor discovers it, trouble can be prevented. This is what security updates are for, which your phone and computer regularly request.

With AI agents, the concept expands. Here, not only the program code can be faulty; the operating principle itself can be attacked: the agent follows text instructions, so a sentence hidden in a web page or email can get it to do something other than what you asked.

How it works

  1. Origin: a weakness is born from a design flaw, programming error, poor configuration, or outdated component, often going unnoticed by anyone.
  2. Discovery: someone finds it. It could be the manufacturer, an independent security researcher, an automated scanning tool, a bug-hunting AI agent, or, in the worst case, an attacker.
  3. Disclosure and registration: the good-faith discoverer informs the manufacturer. Publicly disclosed vulnerabilities typically receive a unique identifier (CVE number) and a severity score (for example, CVSS score) so that everyone is talking about the same thing.
  4. Fix: the manufacturer releases a security update (a fix package, or patch). The bug does not disappear on your end: it only goes away once you install the update.
  5. Exploitation: if the attacker is faster than the patch or update installation, they can steal data, take control, or disable the system through the vulnerability. Attackers sometimes exploit a flaw even when the manufacturer is unaware of it or no fix exists yet. This is called a zero-day vulnerability.

An everyday example

Your phone sends a notification in the evening that an important security update is available, and you tap the 'Later' button. The update would likely fix a known vulnerability, meaning while you delay, your device operates with a flaw that attackers may also know about.

Who is affected

everyoneEvery phone, router, and application can have vulnerabilities, and you can do a lot to counter them by installing updates.
entrepreneur, executiveAn unpatched vulnerability can lead to data loss, downtime, and fines, so the order of fixes is also a matter of managerial responsibility.
developerYou are responsible for bugs in your code and in the external packages used, and you must verify the code written by the coding agent just the same. → Code
bank customer, investorMost bank fraud relies on deception, but vulnerabilities in a phone or browser that has not been updated can also open a path for malware to your money and data. → Money

A common misconception

MythIf a vulnerability is found in a program, the program is bad and has surely already been hacked.
In realityVirtually all software contains vulnerabilities, and discovering them is mostly good news because they can then be fixed. The trouble begins if the bug is not fixed, or if you do not install the update.

Limits and risks

Similar, but not the same

Related concepts

Broader

cybersecurity, information security, AI safety, risk management

Narrower

zero-day vulnerability, prompt injection

On the edge

exploit, threat, security update, attack surface, red teaming, jailbreak, data poisoning

A brief history

Software vulnerabilities are as old as computer networks: the 1988 Morris worm spread by exploiting such flaws. The US-based MITRE launched the CVE list in 1999, which since then has provided a standard identifier for publicly known vulnerabilities.

Where things stand

Vulnerability management is a basic everyday task in cybersecurity by the end of 2026. Under the EU Cyber Resilience Act, from September 11, 2026, manufacturers of digital products must report actively exploited vulnerabilities in their products to the authorities quickly, initially within 24 hours. AI shapes the field in two ways: agents speed up the discovery of flaws, while also introducing new weak points that are hard to fix.

Status: 2026 November

In the news

Appears in 25 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Also known as

vulnerability · vulnerability · security vulnerability · security flaw · gyenge pont · vulnerability · security flaw · CVE

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.