Administrația Națională „Apele Române”
Last Update: 2025-12-24
Between 600 and 649
None
NAICS: 92
NAICS Definition: Public Administration
Employees: 55
Subsidiaries: 0
12-month incidents
1
Known data breaches
0
Attack type number
1
Comparison Overview
Administrația Națională „Apele Române”
VS
City of Tallinn
City of Tallinn
Last Update: 2025-12-17
Between 750 and 799
Tallinn is the capital of Estonia. The mission of the city organization is to make Tallinn the best place to live for the people staying here, the desired destination for people arriving here, and a good place of departure for people who start here. For this purpose, the management of Tallinn as an organization is human-centered, transparent, and cooperative. The city is managed on the basis of a Tallinn 2035 development strategy and other development documents are based thereon. The development strategy is the social agreement of the citizens on what their city should be like in the future. The city communicates with the public and stakeholders in a manner that is open and understandable, and it is easy for people to communicate with the city in turn. The city organization is an organization that learns and works together, it is built in consideration of objectives and performance and its structure adapts over time. The management decisions of the city are based on knowledge and data. New approaches and new solutions are tested. On this account, we share the latest news from the city of Tallinn and its organizations. Show more Show less
NAICS: 922
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Compliance Badges Comparison
Security & Compliance Standards Overview
Administrația Națională „Apele Române”
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
City of Tallinn
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Administrația Națională „Apele Române”
100%
Compliance Rate
0/4 Standards Verified
City of Tallinn
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Average (This Year)
Administrația Națională „Apele Române” has 19.05% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Average (This Year)
No incidents recorded for City of Tallinn in 2025.
Incident History — Administrația Națională „Apele Române” (X = Date, Y = Severity)
Administrația Națională „Apele Române” cyber incidents detection timeline including parent company and subsidiaries
Incident History — City of Tallinn (X = Date, Y = Severity)
City of Tallinn cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Administrația Națională „Apele Române”
Incidents
City of Tallinn
Incidents
No Incident
FAQ
City of Tallinn company demonstrates a stronger AI Cybersecurity Score compared to Administrația Națională „Apele Române” company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Administrația Națională „Apele Române” company has historically faced a number of disclosed cyber incidents, whereas City of Tallinn company has not reported any.
In the current year, Administrația Națională „Apele Române” company has reported more cyber incidents than City of Tallinn company.
Administrația Națională „Apele Române” company has confirmed experiencing a ransomware attack, while City of Tallinn company has not reported such incidents publicly.
Neither City of Tallinn company nor Administrația Națională „Apele Române” company has reported experiencing a data breach publicly.
Neither City of Tallinn company nor Administrația Națională „Apele Române” company has reported experiencing targeted cyberattacks publicly.
Neither Administrația Națională „Apele Române” company nor City of Tallinn company has reported experiencing or disclosing vulnerabilities publicly.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds any compliance certifications.
Neither company holds any compliance certifications.
Neither Administrația Națională „Apele Române” company nor City of Tallinn company has publicly disclosed detailed information about the number of their subsidiaries.
City of Tallinn company employs more people globally than Administrația Națională „Apele Române” company, reflecting its scale as a Government Administration.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds SOC 2 Type 1 certification.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds SOC 2 Type 2 certification.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds ISO 27001 certification.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds PCI DSS certification.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds HIPAA certification.
Neither Administrația Națională „Apele Române” nor City of Tallinn holds GDPR certification.
Latest Global CVEs (Not Company-Specific)
Description
httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.
Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.
Risk Information
cvss3
Base: 9.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Description
continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.
Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
- https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62
- https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcore%401.1.8
- https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3
- https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6
Description
LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.
Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
References
- https://github.com/langchain-ai/langchain/commit/5ec0fa69de31bbe3d76e4cf9cd65a6accb8466c8
- https://github.com/langchain-ai/langchain/commit/d9ec4c5cc78960abd37da79b0250f5642e6f0ce6
- https://github.com/langchain-ai/langchain/pull/34455
- https://github.com/langchain-ai/langchain/pull/34458
- https://github.com/langchain-ai/langchain/releases/tag/langchain-core%3D%3D0.3.81
- https://github.com/langchain-ai/langchain/releases/tag/langchain-core%3D%3D1.2.5
- https://github.com/langchain-ai/langchain/security/advisories/GHSA-c67j-w6g6-q2cm
