AIM SHIELD Emergency
Prioritise your report · Free

What do you fix first in your vulnerability report?

Upload or paste your scanner's report and we give you a list in Spanish: first what is already being used to attack, then the most likely and the most serious. Grouped by device and program, with what your report says to fix it.

We keep nothing. The report is analysed on the spot, in memory, and is not recorded in any log. We do not open or follow any link in your report.

Which files we read

JSON from container scanners, JSON or JSONL from template scanners, SARIF, and CSV from network scanners. Up to 5 MB. If the file is in another format, we tell you.

Your report

What we have seen

Right now we do not have the catalogue of exploited flaws downloaded. We sort only by the severity from your scanner.

Your report is very long: we have read only the first findings. Split it to see the rest.

How we sort

Fix this first
The flaw is in the catalogue of flaws already being used in attacks (CISA).
Next: high probability
The probability of it being attacked in the next 30 days is high (EPSS). Right now this tier is switched off.
Next: serious
Your scanner marks them as critical or high.
The rest
The rest, from most to least serious.

For the programs on a computer, see My programs. If you need it as evidence, see the NIS2 file.

Frequently asked questions

Do you keep my report?

No. The report is analysed instantly, in memory, and is not saved or written to any log: neither the text nor the names of your computers or packages. If you close the page, it disappears.

Which files can I use?

These formats: container scanner JSON, template scanner JSON or JSONL, SARIF and network scanner CSV. You can upload the file (up to 5 MB) or paste its contents. If the file is in another format, we tell you: we don't guess.

In what order is the list shown?

First, whatever is in the catalogue of flaws already used in attacks (CISA). Then, whatever has a high probability of attack according to EPSS. Then, whatever your scanner marks as critical or high. And lastly, the rest. Within each tier, from most to least likely and from most to least serious.

What do I do about each flaw?

We give you what your own report says: the version that fixes the flaw or the solution it proposes. If the report doesn't include any, we tell you and send you to the manufacturer's notice. We don't invent fixes.

Why does no flaw appear under “high likelihood”?

That band uses EPSS, which is only available when we have it turned on. If it isn't, the order is still useful: first what is actually being attacked and then the severity from your scanner.

Does “It's in the catalogue” mean I have been attacked?

No. It means that flaw has been used in real attacks against someone. If your computer has the affected version and can be reached, it is the most urgent. If you have already fixed it, run the scanner again.

Is it useful for the NIS2 file?

It serves as proof that you review your vulnerabilities and rank them by risk. Download or save the result yourself if you want to keep it: we don't store it. You have the NIS2 file at /expediente-nis2.

What happens if you have no catalogue data?

We tell you at the top of the result. In that case we only rank by the severity from your scanner.

Sources

Sources consulted on 1 November 2026. The exploited flaws are those of the public catalogue of the US cybersecurity agency (CISA). This tool sorts what your report says; it does not replace it or check it by itself.