Hi Jonathan,
Thank you for opening your question here!
First, what version of notebook are you running? I think this has been addressed in v6.4.4 (see this
changelog). Let me know if that's not true.
To be clear, we didn't "choose" to implement markdown sanitization in response to this CVE. Jupyter Notebook was already doing markdown sanitization, but it was using a deprecated library with a critical security vulnerability. As a result, we were forced to replace that dependency; in doing so, we didn't properly configure the new sanitizer to allow some basic styling. As I mentioned, I hope this was fixed in v6.4.4, but let us know if not and we can start the conversation in a thread.
TL;DR
As an aside, security vulnerabilities are tricky. In this particular case, we were required to act fast, while coordinating effort with multiple people from different organizations (the challenges of open-source). You can read more about it in this
blog post. We did our best with the constraints we had—and we learned some things for next time.
It's also important to keep in mind that there is a relatively small number of people working on core Jupyter components, while the project generates a large volume of work for everyone. As you know from the future of the notebook discussions, Notebook maintainers are spread pretty thin these days. This issue specifically was one of the main factors that prompted the wider discussion about Notebook's future.
Thank you again, Jonathan. I hope you're able to get your notebooks working again with a later release of Notebook.
Best,
Zach Sailer, Ph.D.
Apple | Sr. Software Engineer
Project Jupyter | Core Developer