Comparison Overview
A1 Srbija d.o.o.

A1 Srbija d.o.o.
Milutina Milankovića 1ž, Belgrade, 11000, RS
Last Update: 20/04/2026
A1 Serbia is a part of A1 Telekom Austria Group, leading provider of digital services and communications solutions in Central and Eastern Europe. Together we are offering a state-of-the art network infrastructure and strive to empower digital life of more than 25 millio...

Vodafone
1 Kingdom Street, London, W2 6BY, GB
Last Update: 08/09/2026
At Vodafone, our purpose is to connect everyone. From the seabed to the stars, we provide innovative mobile and fixed connectivity solutions to empower our customers across the globe. And we're constantly expanding coverage to bridge continents and spread inclusion, eve...
Compliance Ranges Comparison

A1 Srbija d.o.o.







Vodafone






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for A1 Srbija d.o.o. in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Vodafone has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - A1 Srbija d.o.o. (X = Date, Y = Severity)
A1 Srbija d.o.o. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vodafone (X = Date, Y = Severity)
Vodafone cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

A1 Srbija d.o.o.

Vodafone
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.