Comparison Overview
Access Dental Lab

Access Dental Lab
601 Bakertown Rd, Nashville, US
Last Update: 08/12/2025
Access Dental Lab is where dreams of a new and confident smile are made a reality. In partnership with SmileDirectClub, we ultilize recent trends in 3D printing and telehealth to bring about a disruptive change in the invisible aligner market. Our passionate and energet...

Coty
Buitenveldertselaan 3-5, Amsterdam, 1082, NL
Last Update: 03/04/2026
Since 1904, Coty has fearlessly pioneered innovation across the beauty industry. We have a reputation for breaking new ground; a history of ‘firsts’ and ‘bests’ that has laid the foundation for the industry as we know it today. For over a century, our brands have been ...
Compliance Ranges Comparison

Access Dental Lab







Coty






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Access Dental Lab in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Coty in 2026.
Incident History - Access Dental Lab (X = Date, Y = Severity)
Access Dental Lab cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coty (X = Date, Y = Severity)
Coty cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Access Dental Lab

Coty
FAQ
Latest Global CVEs
MojoX::Authentication versions before 0.006 for Perl allow SAML authentication bypass because parse_assertion builds Net::SAML2::Binding::POST without a trust anchor. parse_assertion in MojoX::Authentication::Model::SAML2 calls Net::SAML2::Binding::POST->new with no cacert, cert_text or anchors argument, then passes the returned XML to Net::SAML2::Protocol::Assertion->new_from_xml with the IdP signing certificate as cacert. In Net::SAML2 before 0.86 that certificate guards only encrypted assertions, so the signature on an unencrypted assertion is checked against the certificate the response itself carries. An attacker starts a SAML login, then posts a response signed with a certificate of their own. The audience, InResponseTo and timestamp checks that follow are all satisfiable by the attacker, so the response authenticates any NameID it carries.
A weakness has been identified in itsourcecode Sales and Inventory System 1.0. Affected by this vulnerability is an unknown functionality of the file /pages/sup_del.php?type=supplier. Executing a manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.
A security flaw has been discovered in mwiede jsch up to 2.28.5. Affected is the function getRevokedKeys of the file src/main/java/com/jcraft/jsch/KnownHosts.java. Performing a manipulation of the argument known_hosts results in improper check for certificate revocation. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is told to be difficult. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.28.6 is able to address this issue. The patch is named 194a2f76a5c0f1c3f778565be3fd66bcafc42d23. You should upgrade the affected component.
- https://github.com/mwiede/jsch/
- https://github.com/mwiede/jsch/commit/194a2f76a5c0f1c3f778565be3fd66bcafc42d23
- https://github.com/mwiede/jsch/issues/1091
- https://github.com/mwiede/jsch/pull/1098
- https://github.com/mwiede/jsch/releases/tag/jsch-2.28.6
- https://vuldb.com/cve/CVE-2026-86231
- https://vuldb.com/submit/898485
- https://vuldb.com/vuln/399388
- https://vuldb.com/vuln/399388/cti
A security vulnerability has been detected in JeecgBoot up to 3.9.3. This vulnerability affects the function exportXls of the file jeecg-boot/jeecg-boot-module/jeecg-boot-module-airag/src/main/java/org/jeecg/modules/airag/llm/controller/AiragModelController.java. Such manipulation of the argument credential leads to improper access controls. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 3.9.5 is able to resolve this issue. The name of the patch is a2be896f753936956ee6863b632b8e5a0231345c. You should upgrade the affected component.
- https://github.com/jeecgboot/JeecgBoot/
- https://github.com/jeecgboot/JeecgBoot/commit/a2be896f753936956ee6863b632b8e5a0231345c
- https://github.com/jeecgboot/JeecgBoot/issues/9600
- https://github.com/jeecgboot/JeecgBoot/releases/tag/v3.9.5
- https://vuldb.com/cve/CVE-2026-86228
- https://vuldb.com/submit/898368
- https://vuldb.com/vuln/399381
- https://vuldb.com/vuln/399381/cti
A weakness has been identified in valkey-io valkey up to 9.0.5/9.1.1. This affects the function kvstoreGetHashtable of the file src/kvstore.c. This manipulation of the argument didx causes out-of-bounds read. It is possible to initiate the attack remotely. The attack is considered to have high complexity. It is indicated that the exploitability is difficult. The exploit has been made available to the public and could be used for attacks. Patch name: 4691888e7fab3df128f0bde5750c9fde2ae552fa. To fix this issue, it is recommended to deploy a patch. Exploitation requires cluster mode plus attacker-controlled dump.rdb at startup (data-dir write access, replication feed, or a stored crafted RDB) - an attacker-position DoS at boot, not network pre-auth. The issue report was closed stating it "is worth fixing for the sake of memory safety… but I don't think it meets our bar for a security disclosure."
- https://github.com/user-attachments/files/30195539/RDB.zip
- https://github.com/valkey-io/valkey/
- https://github.com/valkey-io/valkey/commit/4691888e7fab3df128f0bde5750c9fde2ae552fa
- https://github.com/valkey-io/valkey/issues/4222
- https://github.com/valkey-io/valkey/pull/4229
- https://vuldb.com/cve/CVE-2026-86227
- https://vuldb.com/submit/897659
- https://vuldb.com/vuln/399380
- https://vuldb.com/vuln/399380/cti