<a href="https://www.icann.org/news/blog/update-on-icann61-adobe-connect-issues">https://www.icann.org/news/blog/update-on-icann61-adobe-connect-issues</a><div dir="auto"><br></div><div dir="auto">“<span style="font-family:helvetica,arial,sans-serif;font-size:16px">The issue is one that could possibly lead to the disclosure of the information shared in an</span><span style="font-family:helvetica,arial,sans-serif;font-size:16px"> </span><abbr title="Internet Corporation for Assigned Names and Numbers" style="font-family:helvetica,arial,sans-serif;font-size:16px;box-sizing:border-box;unicode-bidi:bidi-override;direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr><span style="font-family:helvetica,arial,sans-serif;font-size:16px"> </span><span style="font-family:helvetica,arial,sans-serif;font-size:16px">Adobe Connect room. We are still investigating the root cause of the issue. We have formulated different scenarios based on authentication, encryption, and software versions, which we are testing in a controlled fashion in attempt to replicate and understand the root cause of the issue.</span></div><p style="box-sizing:border-box;line-height:1.4rem;font-size:16px;margin:0px 0px 1.25rem;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif"></p><div dir="auto">We are working directly with Adobe and with our cloud service provider to learn more.”</div><p></p><div dir="auto"><br></div>